You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Arik Kfir (JIRA)" <ji...@codehaus.org> on 2005/10/05 03:23:11 UTC

[jira] Reopened: (MNG-1021) Build numbers are incremented when they shouldn't

     [ http://jira.codehaus.org/browse/MNG-1021?page=all ]
     
Arik Kfir reopened MNG-1021:
----------------------------


Hi,

I tried again from the trunk (using the same POM I attached previously), and while there is some progress, it still does not work. 

Now the binary and source-code JARs have the same build numbers, but the 'maven-metadata.xml' file (under the version directory) still contains a wrong build number.

In the repo are the following files:
[arik@bzq-179-147-142 0.1-SNAPSHOT]$ ll
total 112
-rw-rw-r--  1 arik arik   309 Oct  5 04:14 maven-metadata.xml
-rw-rw-r--  1 arik arik    32 Oct  5 04:14 maven-metadata.xml.md5
-rw-rw-r--  1 arik arik    40 Oct  5 04:14 maven-metadata.xml.sha1
-rw-rw-r--  1 arik arik 12832 Oct  5 04:14 msg-0.1-20051005.011402-1.jar
-rw-rw-r--  1 arik arik    32 Oct  5 04:14 msg-0.1-20051005.011402-1.jar.md5
-rw-rw-r--  1 arik arik    40 Oct  5 04:14 msg-0.1-20051005.011402-1.jar.sha1
-rw-rw-r--  1 arik arik  3016 Oct  5 04:14 msg-0.1-20051005.011402-1.pom
-rw-rw-r--  1 arik arik    32 Oct  5 04:14 msg-0.1-20051005.011402-1.pom.md5
-rw-rw-r--  1 arik arik    40 Oct  5 04:14 msg-0.1-20051005.011402-1.pom.sha1
-rw-rw-r--  1 arik arik  6924 Oct  5 04:14 msg-0.1-20051005.011402-1-sources.jar
-rw-rw-r--  1 arik arik    32 Oct  5 04:14 msg-0.1-20051005.011402-1-sources.jar.md5
-rw-rw-r--  1 arik arik    40 Oct  5 04:14 msg-0.1-20051005.011402-1-sources.jar.sha1

Which is better than before - but the contents of the maven-metadata.xml file is:
[arik@bzq-179-147-142 0.1-SNAPSHOT]$ cat maven-metadata.xml
<metadata>
  <groupId>org.messages</groupId>
  <artifactId>msg</artifactId>
  <version>0.1-SNAPSHOT</version>
  <versioning>
    <snapshot>
      <timestamp>20051005.011402</timestamp>
      <buildNumber>2</buildNumber>
    </snapshot>
    <lastUpdated>20051005011402</lastUpdated>
  </versioning>
</metadata>

Note that the <buildNumber> is 2 - and not 1 as it should be (I cleaned the repo before building).

Let me know if you need more info.

> 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-3
>  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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org