Sometimes it happens automatically, sometimes it does not (so far under Eclipse 3.7 I've never had problems).
When you suspect or know it didn't happen, you have the possibility to force m2eclipse to update the project dependencies.
Basically you get an empty project with a simple file: (note: I like to use the XML editor directly, not the built in wizards). Again, select create a simple project, fill in the module name (maventest-ejb) and then click next. The module will appear in Eclipse as a separate project with its own .project and .classpath file; on disc the project will have appeared as a subdirectory of the parent project. Open up or refresh the parent pom, you'll find that the plugin has added the module for you there.
For the sake of demonstration purposes I'm going to leave it like this for now (except change the artifact Id to maventest-parent). In the last dialog there is not much to change; do make sure to set the ejb packaging type, this will make sure that the EJB facet is installed in your Eclipse project which can help for example deployment tools to do the right thing (such as JBoss Tools hot-deployment! Unfortunately it has not added the module to dependency management, that you'll have to do yourself. check the project in Eclipse; there is something strange there.
We'll be installing the latest version, which you can simply get through the Eclipse Marketplace. After installation and restarting Eclipse you are ready to go.
Update: m2eclipse has been merged into jboss-tools and is now developed as part of that project.
So fill in how you want to name your project, then afterwards rename the artifact Id in the generated file.
If that doesn't help, you should refresh the parent project and try again.Maven is a wonderful tool, Eclipse is a wonderful tool (well, versions 3.5, 3.6 SR1 and 3.7 anyway).Using the two together creates an even more awesome tool.Here you will probably want to uncheck Download repository indexes at startup to speed up Eclipse startup time - you can always update indexes manually if you really need to.When you create a project which you want to Mavenize, Maven should be the one that controls everything; from the project settings to the dependencies. In the next dialog, select create a simple project. In the third dialog you define the starting structure of the pom.When you investigate the resources however, you'll find this: By default all resources are excluded! Needless to say, remove all exclusions because otherwise these resources will not be on the classpath of your application, which can especially hurt in unit tests. Nothing strange of course, managing dependencies is the main reason you want to use Maven to begin with.I don't know who came up with that, but whenever you create a new project or you update the project configuration, the exclusions will return. But lets see how we can deal with changes to poms from Eclipse. First in dependency management in our parent pom: These are some basic dependencies to be able to compile enterprise code - they should all be in Maven central.Open up the project properties and select the build path.Under the source folders, you'll see all the default Maven folders a module should have.This can be a little icky to setup however, especially if you use an Eclipse prior to version 3.7.The deal is that if you do it the way you are supposed to, you'll have no head aches.