Display what has changed since last release upon updating a plugin to a new
version
-----------------------------------------------------------------------------------
Key: MNG-2296
URL: http://jira.codehaus.org/browse/MNG-2296
Project: Maven 2
Type: New Feature
Components: Repositories, POM, Plugins and Lifecycle, Logging, Dependencies,
Artifacts
Versions: 2.0.4
Reporter: Cédric Vidal
Today, when a new version of a plugin is released, it is automatically
downloaded and this is great because it keeps you up to date. For example, this
morning, a new version of the WAR plugin was released on ibiblio (I had
2.0-beta-2 previously), I got the following trace:
--
[INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates
from ibiblio
Downloading:
http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.0/maven-war-plugin-2.0.pom
1/1K
1K downloaded
Downloading:
http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.0/maven-war-plugin-2.0.jar
1/21K
21/21K
21K downloaded
--
The thing is I got no clue whatsoever of what has changed between versions
2.0-beta-2 and 2.0. If I want to know was has changed, I have to manually go on
the maven site or in the JIRA to figure out what has changed.
It would be great if the list of changes that occured between between the
version which was previously locally installed and the newly installed was
displayed upon update as part of the build.
The trace could be:
--
[INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for updates
from ibiblio
Downloading:
http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.0/maven-war-plugin-2.0.pom
1/1K
1K downloaded
Downloading:
http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-war-plugin/2.0/maven-war-plugin-2.0.jar
1/21K
21/21K
21K downloaded
[INFO] Changes that occured between version 2.0-beta-2 and 2.0 are:
o Added blah blah.
o Corrected bug blah blah.
o Removed blah blah.
--
This feature might depend on adding the list of changes to the POM, which might
be an issue since Maven is stable now. But that might not be such a bug deal
since that POM information would most likely be optional.
The changes part of the POM could be structured like Maven 1 Changes plugin's
changes.xml file:
http://maven.apache.org/maven-1.x/plugins/changes/
<releases>
<release version="2.0" date="in CVS">
<action dev="vmassol" type="update">
Blah blah.
</action>
</release>
<release version="1.0" date="2003-06-05" description ="First stable
release.">
<action dev="vmassol" type="add">
Added blah blah.
</action>
<action dev="vmassol" type="fix" issue="JIRA-XXX">
Corrected bug blah blah.
</action>
<action dev="vmassol" type="remove" due-to="John Doe"
due-to-email="[EMAIL PROTECTED]">
Removed blah blah.
</action>
</release>
</releases>
--
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
