[ http://jira.codehaus.org/browse/MECLIPSE-15?page=comments#action_74829 ] Olle Hallin commented on MECLIPSE-15: -------------------------------------
I found a work-around: Simply bind the plugin to a later phase in the build cycle. Example: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-eclipse-plugin</artifactId> <executions> <execution> <phase>process-classes</phase> </execution> </executions> </plugin> > "Provided" dependencies not included in eclipse build path > ---------------------------------------------------------- > > Key: MECLIPSE-15 > URL: http://jira.codehaus.org/browse/MECLIPSE-15 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: Windows XP SP2, J2SE 5.0, running against main trunk in > SVN. > Reporter: Nathaniel Stoddard > Assigned To: Kenney Westerhof > > When an eclipse project is generated for a project with a dependency whose > scope is "provided", the dependency is not included in the build path of the > project. -- 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
