| Issue 319: | Support for war dependencies from repository | |
| 6 people starred this issue and may be notified of changes. | Back to list |
It seems that q4e only support war-type dependencies if they are present as a n opened project in the eclipse workspace. If you close the war project, the main project is no longer able to compile. |
|
,
Mar 14, 2008
After some investigations : the default maven war overlay does not include the war classes or libraries in the classpath. But this is supported by the warpath plugin : http://static.appfuse.org/maven-warpath-plugin/index.html With Q4e and warpath, war's libraries are added to the classpath but not the classes contained in the war. (with mvn compile, everything is added to the classpath) Since the defaut war overlay behavior is quite limited, it would be great if q4e could fully support war dependencies and warpath. |
|
,
Mar 14, 2008
The Candy for Appfuse project used to support integrating the warpath plug-ín into eclipse. Since I'm the author of that plug-in, I'll be eventually merging the changes into q4e or reworking Candy for Appfuse as an extension for q4e. |
|
,
May 09, 2008
Could you provide a test case (some simple projects) for testing war resolution? Regarding warpath support, please open a different issue with the details (and projects needed for testing). |
|
 Sign in to add a comment
|
