[
http://jira.codehaus.org/browse/MSHARED-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=253982#action_253982
]
Neil Tingley commented on MSHARED-169:
--------------------------------------
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.
> *-SNAPSHOT.jar referenced in manifest as *-20101029.223815-3.jar
> ----------------------------------------------------------------
>
> Key: MSHARED-169
> URL: http://jira.codehaus.org/browse/MSHARED-169
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-archiver
> Affects Versions: maven-archiver-2.4
> Environment: Maven 2.2.1 and Maven 3.0. Linux build machine and
> Windows xp development box
> Reporter: Martin Jozef Jamszolik
> Priority: Critical
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
