You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/08/23 05:25:04 UTC
[jira] Created: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
----------------------------------------------------------------------------------------------
Key: MNG-775
URL: http://jira.codehaus.org/browse/MNG-775
Project: Maven 2
Type: New Feature
Components: maven-archiver
Versions: 2.0-alpha-3
Reporter: John Casey
Assigned to: John Casey
Fix For: 2.0-beta-1
>From MNG-251:
bit of a chicken and egg problem under the current arch. I want to include:
- the build number as a separate manifest entry
- the correct version in the manifest and META-INF/maven/pom.xml
However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
More thinking required.
--
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-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=all ]
John Casey closed MNG-775:
--------------------------
Resolution: Fixed
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
> Original Estimate: 6 hours
> Time Spent: 6 hours
> Remaining: 0 minutes
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=all ]
John Casey updated MNG-775:
---------------------------
Remaining Estimate: 6 hours
Original Estimate: 21600
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
> Original Estimate: 6 hours
> Remaining: 6 hours
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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] Commented: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=comments#action_44997 ]
John Casey commented on MNG-775:
--------------------------------
If we're to have a single snapshot build-id for artifacts and attachments, then it will have to be generated ahead of the install/deploy process, which means it's a no-brainer to also include in the artifacts themselves, somewhere under META-INF possibly.
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=all ]
Brett Porter updated MNG-775:
-----------------------------
Fix Version: (was: 2.0-beta-4)
2.1
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Priority: Minor
> Fix For: 2.1
>
> Original Estimate: 6 hours
> Time Spent: 6 hours
> Remaining: 0 minutes
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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] Commented: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=comments#action_44998 ]
John Casey commented on MNG-775:
--------------------------------
single build number is used per artifact-set (artifact plus attachments, defined by g:a), but NOT per reactor, since individual builds of sub-projects could lead to build numbers falling out of sync.
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=all ]
Brett Porter updated MNG-775:
-----------------------------
Assign To: (was: John Casey)
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Fix For: 2.0-beta-2
>
> Original Estimate: 6 hours
> Time Spent: 6 hours
> Remaining: 0 minutes
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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] Commented: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=comments#action_44996 ]
John Casey commented on MNG-775:
--------------------------------
I'm recreating this issue, to properly account for time.
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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] Reopened: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-775?page=all ]
Brett Porter reopened MNG-775:
------------------------------
rolled back. wasn't working.
due to low priority, we'll leave this for later.
> Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-775
> URL: http://jira.codehaus.org/browse/MNG-775
> Project: Maven 2
> Type: New Feature
> Components: maven-archiver
> Versions: 2.0-alpha-3
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.0-beta-1
>
> Original Estimate: 6 hours
> Time Spent: 6 hours
> Remaining: 0 minutes
>
> From MNG-251:
> bit of a chicken and egg problem under the current arch. I want to include:
> - the build number as a separate manifest entry
> - the correct version in the manifest and META-INF/maven/pom.xml
> However, the snapshot is only determined when the artifact is transformed for install - which comes after package.
> I think this may need to be a phase before package, or part of an existing phase, or that packaging actually does the version assignment, and install/deploy just utilises it.
> More thinking required.
--
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