The following comment has been added to this issue:
Author: Brett Porter
Created: Thu, 26 Feb 2004 11:59 AM
Body:
plugin release technique clarified. Each must have a release.
Bundled with maven is just the latest version of each. This is done by scanning a cvs
checkout, getting the project.xml files, and reading the <versions/> section to find
the last entry (entry at bottom is always most recent, and this is mandated by the
release transformer tag).
Still to do: write the code to build a maven release in this way
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1105&page=comments#action_17168
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1105
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-1105
Summary: resolve plugin release technique when bundling with maven core
Type: Task
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
planning
Fix Fors:
1.0-final
Versions:
1.0-rc1
Assignee:
Reporter: Brett Porter
Created: Thu, 1 Jan 2004 3:33 PM
Updated: Thu, 26 Feb 2004 11:59 AM
Description:
should plugin releases really be made via maven:release, ala RC1? It doesn't do
standard tagging/announce/changes.xml update, etc right now.
Perhaps manually release all snapshots before building bundled maven, or use old
versions in bundle, by specifying somehow.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
