You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2005/09/10 03:16:02 UTC
[jira] Created: (MNG-861) Build number in the maven-metadata.xml appears to one behind the actual build number
Build number in the maven-metadata.xml appears to one behind the actual build number
------------------------------------------------------------------------------------
Key: MNG-861
URL: http://jira.codehaus.org/browse/MNG-861
Project: Maven 2
Type: Bug
Reporter: Jason van Zyl
Fix For: 2.0-beta-1
I deployed plexus-container-default a couple of times and it appears the buildNumber field showed actualBuildNumber-1. The artifacts were deployed with TIMESTAMP-B# and in the metadata the bulidNumber = B#-1. This results in metadata not being found and in this particular case prevented me from bootstrapping.
--
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
[jira] Closed: (MNG-861) Build number in the maven-metadata.xml appears to one behind the actual build number
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-861?page=all ]
Brett Porter closed MNG-861:
----------------------------
Assign To: Brett Porter (was: Jason van Zyl)
Resolution: Fixed
> Build number in the maven-metadata.xml appears to one behind the actual build number
> ------------------------------------------------------------------------------------
>
> Key: MNG-861
> URL: http://jira.codehaus.org/browse/MNG-861
> Project: Maven 2
> Type: Bug
> Reporter: Jason van Zyl
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
>
> I deployed plexus-container-default a couple of times and it appears the buildNumber field showed actualBuildNumber-1. The artifacts were deployed with TIMESTAMP-B# and in the metadata the bulidNumber = B#-1. This results in metadata not being found and in this particular case prevented me from bootstrapping.
--
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
[jira] Updated: (MNG-861) Build number in the maven-metadata.xml appears to one behind the actual build number
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-861?page=all ]
Jason van Zyl updated MNG-861:
------------------------------
Assign To: Brett Porter
I manually edited the metadata on beaver: i adjusted the buildNumber to match the deployed artifact to see if I could get things to work. It appears to have made things work. So I think there's definitely a little quirk in the rewriting of the metadata.
> Build number in the maven-metadata.xml appears to one behind the actual build number
> ------------------------------------------------------------------------------------
>
> Key: MNG-861
> URL: http://jira.codehaus.org/browse/MNG-861
> Project: Maven 2
> Type: Bug
> Reporter: Jason van Zyl
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
>
> I deployed plexus-container-default a couple of times and it appears the buildNumber field showed actualBuildNumber-1. The artifacts were deployed with TIMESTAMP-B# and in the metadata the bulidNumber = B#-1. This results in metadata not being found and in this particular case prevented me from bootstrapping.
--
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