Maven Shared Components

*-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Critical Critical
  • Resolution: Unresolved
  • Affects Version/s: maven-archiver-2.4
  • Fix Version/s: None
  • Component/s: maven-archiver
  • Labels:
    None
  • Environment:
    Maven 2.2.1 and Maven 3.0. Linux build machine and Windows xp development box
  • Number of attachments :
    0

Description

Build involves an EAR, WAR and JAR projects.
Steps to reproduce:

1)project business.jar hold dependency on project security.jar
2)security.jar is accessible only from remote repository (important!) and as an snapshot. ( ex security-10.04.20-20101029.223815-3.jar)
3)business.jar adds classpath entries to manifest as security-10.04.20-20101029.223815-3.jar.
4)business.jar and security.jar get packaged in an EAR as business-SNAPSHOT.jar and security-SNAPSHOT.jar.
On startup application fails to load due to unresolved compilation errors. security-10.04.20-20101029.223815-3.jar cannot be found.

I believe that the entry in the manifest should have been security-SNAPSHOT.jar to match the actual jar that's copied into the ear or war.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Martin Jozef Jamszolik added a comment -

After studying maven-archiver code. I used <useUniqueVersions>false</useUniqueVersions> under <manifest> tag and that seems to correct the mismatch. However, I find it disturbing that the default configuration breaks the project runtime until we add this configuration flag. Hence i still believe it's a bug.

Show
Martin Jozef Jamszolik added a comment - After studying maven-archiver code. I used <useUniqueVersions>false</useUniqueVersions> under <manifest> tag and that seems to correct the mismatch. However, I find it disturbing that the default configuration breaks the project runtime until we add this configuration flag. Hence i still believe it's a bug.
Hide
Permalink
Neil Tingley added a comment -

I think its still broken in maven 3. Have been having exactly the same problem.

Adding <useUniqueVersions>false</useUniqueVersions> under <configuration/> didn't work - are the docs correct ?

Will adding that config in the manifest section instead.

Show
Neil Tingley added a comment - I think its still broken in maven 3. Have been having exactly the same problem. Adding <useUniqueVersions>false</useUniqueVersions> under <configuration/> didn't work - are the docs correct ? Will adding that config in the manifest section instead.
Hide
Permalink
Neil Tingley added a comment -

BTW all is fine in maven 2.2.1 however have forced non-unique snapshots in <distributionManagement> so perhaps its always going to behave like that.

Show
Neil Tingley added a comment - BTW all is fine in maven 2.2.1 however have forced non-unique snapshots in <distributionManagement> so perhaps its always going to behave like that.

People

  • Assignee:
    Unassigned
    Reporter:
    Martin Jozef Jamszolik
Vote (1)
Watch (1)

Dates

  • Created:
    Updated: