[ http://jira.codehaus.org/browse/MECLIPSE-129?page=comments#action_70175 ] Martin Heitz commented on MECLIPSE-129: ---------------------------------------
Additionally to my use case this is necessary if having two .war projects: The first one contains standard web stuff (e.g. a basic MVC-Framework), the second one contains project-specific stuff (e.g. extensions of the MVC-Framework classes). > dependent .war files should be resolved and added to classpath > -------------------------------------------------------------- > > Key: MECLIPSE-129 > URL: http://jira.codehaus.org/browse/MECLIPSE-129 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution > Reporter: Martin Heitz > > To set up an integration test eclipse project, I have a dependency to a WAR > file containing a web service implementation. But the classes from the war > file are not visible in the generated Eclipse project. > In other words: the web service project is contained in the .project, but not > in the generated .classpath file. > Wish: .war files, where a project depends upon, should become part of the > generated .classpath; > dependencies which arise by the .war file should be added also to the > generated .classpath. > Best regards from sunny Black Forrest, Germany, > Mattin -- 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
