jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x Eclipse Plugin
  • MECLIPSE-431

Non-project EJB dependencies need a version number in application.xml

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.5.1
  • Fix Version/s: None
  • Component/s: RAD support, WTP support
  • Labels:
    None
  • Patch Submitted:
    Yes

Description

This relates to issue MECLIPSE-430. When including EJBs that were built previously (ie, not part of the same multi-module project as the ear), the application.xml needs to include their version number.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    MECLIPSE_431.3.patch
    03/Mar/09 3:17 PM
    2 kB
    Elmar Bomberg
  2. Text File
    MECLIPSE_431.4.patch
    04/Mar/09 8:44 AM
    2 kB
    Elmar Bomberg
  3. Text File
    MECLIPSE-431.2.patch
    15/Dec/08 3:23 PM
    2 kB
    Dan Sullivan
  4. Text File
    MECLIPSE-431.patch
    11/Apr/08 12:28 PM
    2 kB
    Michael Johns

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-466 application.xml generated incorrectly for 3rd party ejb modules

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is related to

Bug - A problem which impairs or prevents the functions of the product. MECLIPSE-430 Non-project EJB dependencies should not be placed in the .modulemaps file

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Dan Sullivan added a comment - 15/Dec/08 3:23 PM

The same problem exists for the EclipseWtpApplicationXMLWriter as for the RadApplicationXMLWriter.

Show
Dan Sullivan added a comment - 15/Dec/08 3:23 PM The same problem exists for the EclipseWtpApplicationXMLWriter as for the RadApplicationXMLWriter.
Hide
Permalink
Elmar Bomberg added a comment - 03/Mar/09 3:17 PM

The patch MECLIPSE_431.2 does not work in all cases. In our application.xml the version-number was resolved as timestamp-version. But the name of the referenced jar was xxx-SNAPSHOT. I would suggest the patch MECLIPSE_431.3.

This patch uses (dependency.getFile().getName()) instead of ("dependency.getArtifactId() + "-" + dependency.getVersion() + ".jar")

Show
Elmar Bomberg added a comment - 03/Mar/09 3:17 PM The patch MECLIPSE_431.2 does not work in all cases. In our application.xml the version-number was resolved as timestamp-version. But the name of the referenced jar was xxx-SNAPSHOT. I would suggest the patch MECLIPSE_431.3. This patch uses (dependency.getFile().getName()) instead of ("dependency.getArtifactId() + "-" + dependency.getVersion() + ".jar")
Hide
Permalink
Elmar Bomberg added a comment - 04/Mar/09 8:44 AM

I also corrected the RadApplicationXMLWriter with Patch MECLIPSE_431.4.

Show
Elmar Bomberg added a comment - 04/Mar/09 8:44 AM I also corrected the RadApplicationXMLWriter with Patch MECLIPSE_431.4.
Hide
Permalink
Robrecht Anrijs added a comment - 12/Jul/11 1:39 AM

patch MECLIPSE_431.4 and MECLIPSE_431.3 are working. I was wondering when these bugs are being fixed in the plugin. Is this plugin end of life?

Show
Robrecht Anrijs added a comment - 12/Jul/11 1:39 AM patch MECLIPSE_431.4 and MECLIPSE_431.3 are working. I was wondering when these bugs are being fixed in the plugin. Is this plugin end of life?
Hide
Permalink
Robert Scholte added a comment - 07/Aug/11 6:46 AM

I'm willing to apply these patches, but I'm missing an integration test to verify it (for now and for ever to prevent regression). Would be great if someone could provide one.
See https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/it/ for some examples. These are just mini maven projects hitting the problem.

Show
Robert Scholte added a comment - 07/Aug/11 6:46 AM I'm willing to apply these patches, but I'm missing an integration test to verify it (for now and for ever to prevent regression). Would be great if someone could provide one. See https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/it/ for some examples. These are just mini maven projects hitting the problem.

People

  • Assignee:
    Unassigned
    Reporter:
    Michael Johns
Vote (6)
Watch (4)

Dates

  • Created:
    11/Apr/08 12:28 PM
    Updated:
    07/Aug/11 6:46 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.