[
https://jira.codehaus.org/browse/MECLIPSE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-129.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> dependent .war files should be resolved and added to classpath
> --------------------------------------------------------------
>
> Key: MECLIPSE-129
> URL: https://jira.codehaus.org/browse/MECLIPSE-129
> Project: Maven Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Dependencies resolution and build path
> (.classpath)
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
