[ http://jira.codehaus.org/browse/MNG-1021?page=comments#action_47879 ]
John Casey commented on MNG-1021: --------------------------------- Ah HA! Found it. This is caused by attached artifacts having their own metadata, which is written when the artifact is deployed - over the top of the main artifact. Since these are attachments, they shouldn't change the metadata of the parent artifact. I'll geld the metadata handling on AttachedArtifact, and this should fix the problem. Just waiting for SVN to come back up before I can commit. > Build numbers are incremented when they shouldn't > ------------------------------------------------- > > Key: MNG-1021 > URL: http://jira.codehaus.org/browse/MNG-1021 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Environment: Fedora 4, JDK 1.5.0_04, Maven 2 beta 1 > Reporter: Arik Kfir > Assignee: John Casey > Fix For: 2.0-beta-4 > Attachments: pom.xml > > Original Estimate: 3 hours > Time Spent: 4 hours > Remaining: 0 minutes > > I have a project built using m2. I want the project to install/deploy > a source-code JAR along with the binaries JAR (on both the install and > deploy phases). I've added the following section in the pom.xml file: > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-source-plugin</artifactId> > <executions> > <execution> > <goals> > <goal>jar</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > </build> > It works very nice, except for one problem: the sources JAR always > gets a new build number. For instance, assuming I clean my local repo, > and then run "m2 install", the local repo will contain: > myproject-20050925.155953-1.jar > myproject-20050925.155953-2-sources.jar > Shouldn't they have the same build number? > This causes a problem because the maven-metadata.xml file specifies > that the current build number is 2, and so, projects depending on that > project can't find the file (since there's no binary JAR for build > number 2, only for build 1). -- 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]
