[
http://jira.codehaus.org/browse/MECLIPSE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130064#action_130064
]
Arnaud Heritier commented on MECLIPSE-424:
------------------------------------------
With this command line plugin, each time you receive an updated pom from your
SVN you have to update eclipse settings (mvn eclipse:eclipse) and t reimport
your projects if a new new modules was added. Are you sure that user A did it ?
If you wantsomething automatic you to look at eclipse plugins for maven like
"Maven Eclipse Integration" or "Q4E". (but you'll have less feature for JEE
developments if you need them).
> New submodules do not show up as seperate projects
> --------------------------------------------------
>
> Key: MECLIPSE-424
> URL: http://jira.codehaus.org/browse/MECLIPSE-424
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Multi-projects
> Affects Versions: 2.5.1
> Environment: win xp, eclipse 3.3
> Reporter: Nayan Hajratwala
>
> Scenario:
> 1) User A checks out a maven project from SVN using "Checkout as Maven
> Project". All modules are now listed as seperate projects in Eclipse
> 2) User B creates a new module in the project, and checks it into SVN
> 3) User A updates project
> 4) New module does not show up as a seperate project.
> 5) User A cries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
