Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      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.

        Activity

        Lukasz Kolek created issue -
        Arnaud HERITIER made changes -
        Field Original Value New Value
        Component/s M2Eclipse support [ 13072 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 10:00:37 UTC 2015 [ 1428228037919 ]
        Mark Thomas made changes -
        Workflow jira [ 12720668 ] Default workflow, editable Closed status [ 12750428 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 23:47:18 UTC 2015 [ 1428277638729 ]
        Mark Thomas made changes -
        Workflow jira [ 12958453 ] Default workflow, editable Closed status [ 12995313 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Lukasz Kolek
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development