[jira] Commented: (MNG-2903) Snapshots are being packaged with datestamps in their filename instead of "SNAPSHOT",

["Mario Camou (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284053#comment-284053 ] 

Mario Camou commented on MNG-2903:
----------------------------------

This problem is affecting us, we're using the copy-resources plugin which copies the resource with the -SNAPSHOT name, but the JAR plugin adds the timestamped name to the Manifest. For the moment I've manually added the -SNAPSHOT to the classpath with the manifestEntries/Class-Path tag but it would be excellent to have the plugin work correctly.

> Snapshots are being packaged with datestamps in their filename instead of "SNAPSHOT", 
> --------------------------------------------------------------------------------------
>
>                 Key: MNG-2903
>                 URL: https://jira.codehaus.org/browse/MNG-2903
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.5
>            Reporter: Tim Cederman
>            Priority: Critical
>             Fix For: Issues to be reviewed for 3.x
>
>
> When I run mvn package on a project, it collects all the correct and most recent
> jar files for me in the lib directory, however in the zip file instead
> of naming them <project>-3.0-SNAPSHOT.jar (for example) it will name
> them <project>-20070318.080720-37.jar.  
> Meanwhile in the project's own jar file, the manifest will point to
> ./lib/<project>-3.0-SNAPSHOT.jar.  This means the packaged project does
> not run.
> It doesn't do this for every single dependency snapshot, and I can't
> seem to work out a pattern as to which get named correctly and which
> don't.
> I have two repositories in my pom file:
> <repositories>
> 	<repository>
> 		<id>common-repository</id>
> 		<name> Common Repository</name>
> 		<url>http://repository/common-repository</url>
> 	</repository>
> 	<repository>
> 		<id>snapshot-repository</id>
> 		<name>Trovix Snapshot Repository</name>
> 		<url>http://repository/snapshots</url>
> 		<snapshots>
> 			<enabled>true</enabled>
> 			<updatePolicy>always</updatePolicy>
> 		</snapshots>
> 	</repository>
> </repositories>
> If I try to disable them manually (and use only the local repository),
> the problem persists.  However, this is where it gets weird.  If I
> unplug my network cable - my package file is created perfectly!
> However - if I unplug my network cable with the snapshot repository
> removed, it creates the package incorrectly once again!
> This seems to be the key part of what is making it work (blacklisting
> the snapshot-repository):
> [INFO]    task-segment: [package]
> [INFO]
> ---------------------------------------------------------------------
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] snapshot com:com.benchmark:3.0-SNAPSHOT: checking for updates
> from snapshot-repository
> [WARNING] repository metadata for: 'snapshot
> com:com.benchmark:3.0-SNAPSHOT' could not be retrieved from repository:
>  snapshot-repository due to an error: Error transferring file
> [INFO] Repository 'snapshot-repository' will be blacklisted
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] No tests to run.
> [INFO] [jar:jar]
> I have also run mvn -X package, and the debug log shows that it thinks
> it is collecting all the correct SNAPSHOT named jars, even though it
> then stores the date-stamped ones.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira