[jira] [Closed] (MECLIPSE-258) deployment of war dependencies in eclipse

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MECLIPSE-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MECLIPSE-258.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> deployment of war dependencies in eclipse
> -----------------------------------------
>
>                 Key: MECLIPSE-258
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-258
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)