[ http://jira.codehaus.org/browse/MNG-745?page=comments#action_44640 ]
Bob Allison commented on MNG-745: --------------------------------- I'm not worried about the build ID being part of the artifact, I was looking at the file xxxxxx-SNAPSHOT.version.txt that is placed in the repository in the same directory as the jar file. I updated my SVN tree at 1530 ET today (revision 233262). The source jar is no longer created or deployed (which doesn't bother me, I was going to ask how to suppress it anyway), and the dependent project builds correctly. > Deploying source jar to repository receives wrong name > ------------------------------------------------------ > > Key: MNG-745 > URL: http://jira.codehaus.org/browse/MNG-745 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Versions: 2.0-beta-1 > Environment: Working from SVN revision 233074 > Project defined with <packaging>jar</packaging> > Reporter: Bob Allison > Assignee: John Casey > > > When the source jar is deployed to the repository (both as a release and as a > snapshot), the jar file is named wrong. The jar that is built is named > log4j-3.0-SNAPSHOT-sources.jar (as expected) but when it is deployed to the > repository it is named log4j-3.0-SNAPSHOT-artifactClassifier.artifactType -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
