[ http://jira.codehaus.org/browse/MECLIPSE-8?page=comments#action_58926 ]
Nico Przybylek commented on MECLIPSE-8: --------------------------------------- Since the new release I am not able to use maven2 any longer as I did. The problem is that I have a project with compile errors. I changed a dependency in the projects pom and started an eclipse:eclipse. Because of the compile error maven2 does not update the classpath. So I have to edit the classpath in the eclipse by hand. In my understanding the classpath should be updated or changed at any time when I start an eclipse:eclipse independend if compile error occured or not. This gives me better chances for bug tracking! > Suport sources generator in eclipse plugin > ------------------------------------------- > > Key: MECLIPSE-8 > URL: http://jira.codehaus.org/browse/MECLIPSE-8 > Project: Maven 2.x Eclipse Plugin > Type: Bug > Versions: 2.0 > Reporter: Gilles Scokart > Assignee: fabrizio giustina > Fix For: 2.1 > > > The current eclipse plugin doesn't have suport for code generation like Maven > 1 (see http://maven.apache.org/maven-1.x/reference/plugins/eclipse/). > In maven 2, its probably simpler. The eclipse plugin in should only launch > the build cycle up to process-test-resources. If any plugin is executed in > the source generation or test source generation phase, those plugins will > automatically add the directory to the list of source directory (as described > in http://maven.apache.org/guides/mini/guide-generating-sources.html). -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
