Maven 2 & 3

rar, par and ejb3 archives should not be added to classpath

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

like war files, should be declared in components.xml as

<includesDependencies>true</includesDependencies>
<language>java</language>
<addedToClasspath>false</addedToClasspath>

Issue Links

This issue relates to:
MSHARED-168 addClasspath doesn't add dependencies to RAR artifacts Blocker Open
This issue supercedes:
MRAR-23 CLONE -No MAR packaging (Causes Maven-cobertura-plugin to fail) Major Open
MRAR-17 No RAR packaging (Causes Maven-cobertura-plugin to fail) Major Closed
This issue is depended upon by:
MNGECLIPSE-425 Rar dependencies cause failure to build project Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Herve Boutemy added a comment -

fixed in trunk r644434
waiting for 2.0.9 release before merging change in 2.0.x branch

Show
Herve Boutemy added a comment - fixed in trunk r644434 waiting for 2.0.9 release before merging change in 2.0.x branch
Hide
Permalink
Herve Boutemy added a comment -

fixed in r646967

Show
Herve Boutemy added a comment - fixed in r646967
Hide
Permalink
John Casey added a comment -

Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

Show
John Casey added a comment - Adding fix-for for both 2.0.10 and 2.1.0-M1, since 2.1.0-M1 will actually be released first and may not incorporate all of the eventual issue fixes released in 2.0.10.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.