Uploaded image for project: 'Maven Eclipse Plugin (RETIRED)'
  1. Maven Eclipse Plugin (RETIRED)
  2. MECLIPSE-466

application.xml generated incorrectly for 3rd party ejb modules

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 2.5.1
    • None
    • WTP support
    • None

    Description

      As you may know by default the project version is not added to the project name. In case I have 3rd party ejb modules from a maven repository (jboss seam for example) the version number for those modules is removed from the generated application.xml as well which breaks the WTP deployment: the server can't find the 3rd party ejb jar because it expects the jar also be without the version number.

      Looks like during generation of application.xml there is no distinction made between dependencies from projects and libraries.

      I included a test case.

      Attachments

        1. test-project.tar.gz
          4 kB
          Siarhei Dudzin

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-431 Non-project EJB dependencies need a version number in application.xml

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              svadu Siarhei Dudzin
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: