[
http://jira.codehaus.org/browse/MECLIPSE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier updated MECLIPSE-258:
-------------------------------------
Component/s: M2Eclipse support
> deployment of war dependencies in eclipse
> -----------------------------------------
>
> Key: MECLIPSE-258
> URL: http://jira.codehaus.org/browse/MECLIPSE-258
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: M2Eclipse support, WTP support
> Reporter: Lukasz Kolek
>
> When I create war that depends on other war, maven2 works ok, combining that
> two projects in one war. To do the same in eclipse, adding:
> <wb-resource deploy-path="/" source-path="target/[module-name-version]"/>
> to .settings/org.eclipse.wst.common.component eclipse file does at least that
> eclipse deploys all new jsp/resources from src path and all the rest from
> (previously generated by maven) target, that contains missing files from
> depended wars.
> While it's a kind of work-around, it would be nice to have that as an option
> when creating eclipse files using eclipse:m2eclipse.
--
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
