You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Krull, Stephan" <St...@ecg-leipzig.de> on 2015/03/10 12:01:32 UTC
Release Notes in Plugin Sites
Hello Maven folks,
I wonder if there is a possibility to include release notes for plugin versions into the common maven site structure. the release notes are available via announcement email (i.e. attached mail) or via JIRA issue tracker from i.e. http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
It would be helpful to have that information included in the standard maven site for an (official) plugin. Probably in a new section on the overview page (i.e. http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new menu entry under menu section "Project Information".
What do you think?
Kind regards
Stephan Krull
-----Ursprüngliche Nachricht-----
Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
Gesendet: Dienstag, 10. März 2015 11:38
An: announce@maven.apache.org
Cc: users@maven.apache.org; dev@maven.apache.org
Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Jar Plugin, version 2.6
This plugin provides the capability to build jars.
http://maven.apache.org/plugins/maven-jar-plugin/
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.6</version>
</plugin>
Release Notes - Maven JAR Plugin - Version 2.6
Bugs:
* [MJAR-135] - encoding problem with folder-names
* [MJAR-151] - Error assembling JAR on OS X
* [MJAR-179] - Adding empty files to jar failed with a ZipException : bad CRC checksum
* [MJAR-185] - Update version of plexus-archiver to 2.7.1
* [MJAR-188] - maven-jar-plugin is very slow on machines with slow Unix group lookups
* [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
Improvements:
* [MJAR-178] - Change information on site
* [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
* [MJAR-181] - MavenProject/MavenSession Injection as a paremeter instead as a component.
* [MJAR-182] - Update version of plexus-archiver to 2.6.3
* [MJAR-184] - Update version of plexus-archiver to 2.7
* [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
* [MJAR-187] - Upgrade maven-archiver to 2.6
* [MJAR-190] - Upgrade to maven-plugins version 25 to 26
* [MJAR-191] - Upgrade to maven-plugins parent version 27
Enjoy,
- The Apache Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release Notes in Plugin Sites
Posted by Andreas Gudian <an...@gmail.com>.
In the last two releases of surefire, we included the jira-report in the
site, listing all resolved issues with the appropriate fix-version:
http://maven.apache.org/surefire/maven-surefire-plugin/jira-report.html
Am Dienstag, 10. März 2015 schrieb Karl Heinz Marbaise :
> Hi Stephan,
>
> On 3/10/15 1:26 PM, Krull, Stephan wrote:
>
>> I agree that there is no HUGE benefit to it.
>>
>
> I wasn't talking about a HUGE benefit...I have asked if there is any
> benefit....
>
> I see only see a very very small to more or less no benefit at all......
>
>
> > Just a matter of conformity to common practices.
>
> To which common practices ? All other projects do release notes/changelogs
> manually...(either pages / files) which i don't like to maintain...
>
> Furthermore we have JIRA for every plugins / component...
>
>
>> When you start to release will the release notes from the JIRA version be
>> finished?
>>
>
> JIRA has simply a link to release notes....
>
> Sometimes it happens that the content changes.....or later...The link is
> fixed...but it changes from release to release...
>
> > That way one could append the link of the release notes
> > to the project overview page before the maven
> > site generation for the release starts.
>
> I would definitely prevent doing something manually ([1] there are enough
> manual steps to do...)...which could lead in missing it...
>
>
> I would not vote for integrating the changes plugin if that leads to
>> problems.
>>
>
> Not really problems, but sometimes it happens that issues will be
> changed/added etc. which would result in different Release notes in JIRA
> and on the generated page, cause the page will be generated during the site
> generation process....and will not being changed afterwards...
>
>
> If you have a single project which is released let's say every 3
> months...it's not a problem to do such things...but here we have 49 plugins
> + (I don't know the number currently) of components etc. where we do
> releases[2]...for...You can take a look into the quaterly report[3] which
> gives you an impression how many releases we are doing...
>
> May be someone of the other devs has a better idea...
>
> BTW: That should not prevent you from creating a jira issue for this idea
> ...and you might take a deeper look here into the project and may be you a
> good solution for this or other problem...
>
>
> [1] http://maven.apache.org/developers/release/maven-
> project-release-procedure.html
> [2] http://mail-archives.apache.org/mod_mbox/maven-announce/
> 201503.mbox/browser
> [3] http://mail-archives.apache.org/mod_mbox/maven-announce/
> 201501.mbox/%3C9815490.A2dQluKqs1%40herve-desktop%3E
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
>> Gesendet: Dienstag, 10. März 2015 12:15
>> An: Maven Developers List
>> Betreff: Re: Release Notes in Plugin Sites
>>
>> Hi Stephan,
>>
>> the question on this is: What would be the benefit of this? Or in other
>> words: Will it bring supplemental information?
>>
>> All the information is available as you already mentioned...if you really
>> interested you can find the information....
>>
>> Apart from that i could think of using maven-changes-plugin to handle
>> this...which unfortunately would make the release process more
>> fragile...and which would mean to change the configuration for all 49
>> plugins...(here on apache)...
>>
>> To be honest: Is that really worth the effort...?
>>
>> What do the other devs think?
>>
>> Kind regards
>> Karl Heinz Marbaise
>> On 3/10/15 12:01 PM, Krull, Stephan wrote:
>>
>>> Hello Maven folks,
>>>
>>> I wonder if there is a possibility to include release notes for plugin
>>> versions into the common maven site structure. the release notes are
>>> available via announcement email (i.e. attached mail) or via JIRA issue
>>> tracker from i.e. http://maven.apache.org/plugins/maven-jar-plugin/
>>> issue-tracking.html .
>>>
>>> It would be helpful to have that information included in the standard
>>> maven site for an (official) plugin. Probably in a new section on the
>>> overview page (i.e. http://maven.apache.org/plugins/maven-jar-plugin/
>>> index.html) or a new menu entry under menu section "Project
>>> Information".
>>>
>>> What do you think?
>>>
>>> Kind regards
>>> Stephan Krull
>>>
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
>>> Gesendet: Dienstag, 10. März 2015 11:38
>>> An: announce@maven.apache.org
>>> Cc: users@maven.apache.org; dev@maven.apache.org
>>> Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
>>>
>>> The Apache Maven team is pleased to announce the release of the Apache
>>> Maven Jar Plugin, version 2.6
>>>
>>> This plugin provides the capability to build jars.
>>>
>>> http://maven.apache.org/plugins/maven-jar-plugin/
>>>
>>> <plugin>
>>> <groupId>org.apache.maven.plugins</groupId>
>>> <artifactId>maven-jar-plugin</artifactId>
>>> <version>2.6</version>
>>> </plugin>
>>>
>>> Release Notes - Maven JAR Plugin - Version 2.6
>>>
>>> Bugs:
>>>
>>> * [MJAR-135] - encoding problem with folder-names
>>> * [MJAR-151] - Error assembling JAR on OS X
>>> * [MJAR-179] - Adding empty files to jar failed with a ZipException :
>>> bad CRC checksum
>>> * [MJAR-185] - Update version of plexus-archiver to 2.7.1
>>> * [MJAR-188] - maven-jar-plugin is very slow on machines with slow
>>> Unix group lookups
>>> * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
>>>
>>> Improvements:
>>>
>>> * [MJAR-178] - Change information on site
>>> * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
>>> * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter
>>> instead as a component.
>>> * [MJAR-182] - Update version of plexus-archiver to 2.6.3
>>> * [MJAR-184] - Update version of plexus-archiver to 2.7
>>> * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
>>> * [MJAR-187] - Upgrade maven-archiver to 2.6
>>> * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
>>> * [MJAR-191] - Upgrade to maven-plugins parent version 27
>>>
>>> Enjoy,
>>>
>>> - The Apache Maven team
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
>> commands, e-mail: dev-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: AW: Release Notes in Plugin Sites
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Stephan,
On 3/10/15 1:26 PM, Krull, Stephan wrote:
> I agree that there is no HUGE benefit to it.
I wasn't talking about a HUGE benefit...I have asked if there is any
benefit....
I see only see a very very small to more or less no benefit at all......
> Just a matter of conformity to common practices.
To which common practices ? All other projects do release
notes/changelogs manually...(either pages / files) which i don't like to
maintain...
Furthermore we have JIRA for every plugins / component...
>
> When you start to release will the release notes from the JIRA version be finished?
JIRA has simply a link to release notes....
Sometimes it happens that the content changes.....or later...The link is
fixed...but it changes from release to release...
> That way one could append the link of the release notes
> to the project overview page before the maven
> site generation for the release starts.
I would definitely prevent doing something manually ([1] there are
enough manual steps to do...)...which could lead in missing it...
> I would not vote for integrating the changes plugin if that leads to problems.
Not really problems, but sometimes it happens that issues will be
changed/added etc. which would result in different Release notes in JIRA
and on the generated page, cause the page will be generated during the
site generation process....and will not being changed afterwards...
If you have a single project which is released let's say every 3
months...it's not a problem to do such things...but here we have 49
plugins + (I don't know the number currently) of components etc. where
we do releases[2]...for...You can take a look into the quaterly
report[3] which gives you an impression how many releases we are doing...
May be someone of the other devs has a better idea...
BTW: That should not prevent you from creating a jira issue for this
idea ...and you might take a deeper look here into the project and may
be you a good solution for this or other problem...
[1]
http://maven.apache.org/developers/release/maven-project-release-procedure.html
[2]
http://mail-archives.apache.org/mod_mbox/maven-announce/201503.mbox/browser
[3]
http://mail-archives.apache.org/mod_mbox/maven-announce/201501.mbox/%3C9815490.A2dQluKqs1%40herve-desktop%3E
Kind regards
Karl Heinz Marbaise
>
> -----Ursprüngliche Nachricht-----
> Von: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> Gesendet: Dienstag, 10. März 2015 12:15
> An: Maven Developers List
> Betreff: Re: Release Notes in Plugin Sites
>
> Hi Stephan,
>
> the question on this is: What would be the benefit of this? Or in other
> words: Will it bring supplemental information?
>
> All the information is available as you already mentioned...if you really interested you can find the information....
>
> Apart from that i could think of using maven-changes-plugin to handle this...which unfortunately would make the release process more fragile...and which would mean to change the configuration for all 49 plugins...(here on apache)...
>
> To be honest: Is that really worth the effort...?
>
> What do the other devs think?
>
> Kind regards
> Karl Heinz Marbaise
> On 3/10/15 12:01 PM, Krull, Stephan wrote:
>> Hello Maven folks,
>>
>> I wonder if there is a possibility to include release notes for plugin versions into the common maven site structure. the release notes are available via announcement email (i.e. attached mail) or via JIRA issue tracker from i.e. http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
>>
>> It would be helpful to have that information included in the standard maven site for an (official) plugin. Probably in a new section on the overview page (i.e. http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new menu entry under menu section "Project Information".
>>
>> What do you think?
>>
>> Kind regards
>> Stephan Krull
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
>> Gesendet: Dienstag, 10. März 2015 11:38
>> An: announce@maven.apache.org
>> Cc: users@maven.apache.org; dev@maven.apache.org
>> Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
>>
>> The Apache Maven team is pleased to announce the release of the Apache
>> Maven Jar Plugin, version 2.6
>>
>> This plugin provides the capability to build jars.
>>
>> http://maven.apache.org/plugins/maven-jar-plugin/
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-jar-plugin</artifactId>
>> <version>2.6</version>
>> </plugin>
>>
>> Release Notes - Maven JAR Plugin - Version 2.6
>>
>> Bugs:
>>
>> * [MJAR-135] - encoding problem with folder-names
>> * [MJAR-151] - Error assembling JAR on OS X
>> * [MJAR-179] - Adding empty files to jar failed with a ZipException : bad CRC checksum
>> * [MJAR-185] - Update version of plexus-archiver to 2.7.1
>> * [MJAR-188] - maven-jar-plugin is very slow on machines with slow Unix group lookups
>> * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
>>
>> Improvements:
>>
>> * [MJAR-178] - Change information on site
>> * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
>> * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter instead as a component.
>> * [MJAR-182] - Update version of plexus-archiver to 2.6.3
>> * [MJAR-184] - Update version of plexus-archiver to 2.7
>> * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
>> * [MJAR-187] - Upgrade maven-archiver to 2.6
>> * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
>> * [MJAR-191] - Upgrade to maven-plugins parent version 27
>>
>> Enjoy,
>>
>> - The Apache Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release Notes in Plugin Sites
Posted by Stephen Connolly <st...@gmail.com>.
I agree, publishing a static release notes makes it hard to add in Known
Issues as they are discovered, plus you want to know all the bugs that have
been found in a specific versions also.
Now of course there is the question of who maintains the known issues,
etc... and I agree that we may not be very good at doing that to date...
but that does not mean we should switch to a technology (i.e. pushing the
notes in a static site) that prevents us from updating the known state of a
release easily (which at least JIRA lets us do)
Hopefully when we move from Codehaus JIRA to ASF JIRA we will be better
able to manage our issues etc
On 10 March 2015 at 12:41, Kristian Rosenvold <kr...@gmail.com>
wrote:
> This is a bit of a can of worms, but release notes (=jira issues) may very
> well change after the release. This is a particular problem with deeply
> componentized architectures like maven itself, issues fixed "somewhere" in
> the bowels of the dependency hierarchy may turn out to have value that is
> discovered after the release.
>
> Sometimes such implications can lead to further issues at a higher level.
> Hopefully they're of the "good" type :) Conceptually you could end up with
> an "open" blocker issue after the release, although we do not have a
> tradition for this....
>
> Kristian
>
>
> 2015-03-10 13:26 GMT+01:00 Krull, Stephan <St...@ecg-leipzig.de>:
>
> > I agree that there is no HUGE benefit to it. Just a matter of conformity
> > to common practices.
> >
> > When you start to release will the release notes from the JIRA version be
> > finished? That way one could append the link of the release notes to the
> > project overview page before the maven site generation for the release
> > starts.
> >
> > I would not vote for integrating the changes plugin if that leads to
> > problems.
> >
> >
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> > Gesendet: Dienstag, 10. März 2015 12:15
> > An: Maven Developers List
> > Betreff: Re: Release Notes in Plugin Sites
> >
> > Hi Stephan,
> >
> > the question on this is: What would be the benefit of this? Or in other
> > words: Will it bring supplemental information?
> >
> > All the information is available as you already mentioned...if you really
> > interested you can find the information....
> >
> > Apart from that i could think of using maven-changes-plugin to handle
> > this...which unfortunately would make the release process more
> > fragile...and which would mean to change the configuration for all 49
> > plugins...(here on apache)...
> >
> > To be honest: Is that really worth the effort...?
> >
> > What do the other devs think?
> >
> > Kind regards
> > Karl Heinz Marbaise
> > On 3/10/15 12:01 PM, Krull, Stephan wrote:
> > > Hello Maven folks,
> > >
> > > I wonder if there is a possibility to include release notes for plugin
> > versions into the common maven site structure. the release notes are
> > available via announcement email (i.e. attached mail) or via JIRA issue
> > tracker from i.e.
> > http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
> > >
> > > It would be helpful to have that information included in the standard
> > maven site for an (official) plugin. Probably in a new section on the
> > overview page (i.e.
> > http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new
> > menu entry under menu section "Project Information".
> > >
> > > What do you think?
> > >
> > > Kind regards
> > > Stephan Krull
> > >
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
> > > Gesendet: Dienstag, 10. März 2015 11:38
> > > An: announce@maven.apache.org
> > > Cc: users@maven.apache.org; dev@maven.apache.org
> > > Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
> > >
> > > The Apache Maven team is pleased to announce the release of the Apache
> > > Maven Jar Plugin, version 2.6
> > >
> > > This plugin provides the capability to build jars.
> > >
> > > http://maven.apache.org/plugins/maven-jar-plugin/
> > >
> > > <plugin>
> > > <groupId>org.apache.maven.plugins</groupId>
> > > <artifactId>maven-jar-plugin</artifactId>
> > > <version>2.6</version>
> > > </plugin>
> > >
> > > Release Notes - Maven JAR Plugin - Version 2.6
> > >
> > > Bugs:
> > >
> > > * [MJAR-135] - encoding problem with folder-names
> > > * [MJAR-151] - Error assembling JAR on OS X
> > > * [MJAR-179] - Adding empty files to jar failed with a ZipException :
> > bad CRC checksum
> > > * [MJAR-185] - Update version of plexus-archiver to 2.7.1
> > > * [MJAR-188] - maven-jar-plugin is very slow on machines with slow
> > Unix group lookups
> > > * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
> > >
> > > Improvements:
> > >
> > > * [MJAR-178] - Change information on site
> > > * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
> > > * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter
> > instead as a component.
> > > * [MJAR-182] - Update version of plexus-archiver to 2.6.3
> > > * [MJAR-184] - Update version of plexus-archiver to 2.7
> > > * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
> > > * [MJAR-187] - Upgrade maven-archiver to 2.6
> > > * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
> > > * [MJAR-191] - Upgrade to maven-plugins parent version 27
> > >
> > > Enjoy,
> > >
> > > - The Apache Maven team
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> > commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: Release Notes in Plugin Sites
Posted by Kristian Rosenvold <kr...@gmail.com>.
This is a bit of a can of worms, but release notes (=jira issues) may very
well change after the release. This is a particular problem with deeply
componentized architectures like maven itself, issues fixed "somewhere" in
the bowels of the dependency hierarchy may turn out to have value that is
discovered after the release.
Sometimes such implications can lead to further issues at a higher level.
Hopefully they're of the "good" type :) Conceptually you could end up with
an "open" blocker issue after the release, although we do not have a
tradition for this....
Kristian
2015-03-10 13:26 GMT+01:00 Krull, Stephan <St...@ecg-leipzig.de>:
> I agree that there is no HUGE benefit to it. Just a matter of conformity
> to common practices.
>
> When you start to release will the release notes from the JIRA version be
> finished? That way one could append the link of the release notes to the
> project overview page before the maven site generation for the release
> starts.
>
> I would not vote for integrating the changes plugin if that leads to
> problems.
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
> Gesendet: Dienstag, 10. März 2015 12:15
> An: Maven Developers List
> Betreff: Re: Release Notes in Plugin Sites
>
> Hi Stephan,
>
> the question on this is: What would be the benefit of this? Or in other
> words: Will it bring supplemental information?
>
> All the information is available as you already mentioned...if you really
> interested you can find the information....
>
> Apart from that i could think of using maven-changes-plugin to handle
> this...which unfortunately would make the release process more
> fragile...and which would mean to change the configuration for all 49
> plugins...(here on apache)...
>
> To be honest: Is that really worth the effort...?
>
> What do the other devs think?
>
> Kind regards
> Karl Heinz Marbaise
> On 3/10/15 12:01 PM, Krull, Stephan wrote:
> > Hello Maven folks,
> >
> > I wonder if there is a possibility to include release notes for plugin
> versions into the common maven site structure. the release notes are
> available via announcement email (i.e. attached mail) or via JIRA issue
> tracker from i.e.
> http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
> >
> > It would be helpful to have that information included in the standard
> maven site for an (official) plugin. Probably in a new section on the
> overview page (i.e.
> http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new
> menu entry under menu section "Project Information".
> >
> > What do you think?
> >
> > Kind regards
> > Stephan Krull
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
> > Gesendet: Dienstag, 10. März 2015 11:38
> > An: announce@maven.apache.org
> > Cc: users@maven.apache.org; dev@maven.apache.org
> > Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
> >
> > The Apache Maven team is pleased to announce the release of the Apache
> > Maven Jar Plugin, version 2.6
> >
> > This plugin provides the capability to build jars.
> >
> > http://maven.apache.org/plugins/maven-jar-plugin/
> >
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-jar-plugin</artifactId>
> > <version>2.6</version>
> > </plugin>
> >
> > Release Notes - Maven JAR Plugin - Version 2.6
> >
> > Bugs:
> >
> > * [MJAR-135] - encoding problem with folder-names
> > * [MJAR-151] - Error assembling JAR on OS X
> > * [MJAR-179] - Adding empty files to jar failed with a ZipException :
> bad CRC checksum
> > * [MJAR-185] - Update version of plexus-archiver to 2.7.1
> > * [MJAR-188] - maven-jar-plugin is very slow on machines with slow
> Unix group lookups
> > * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
> >
> > Improvements:
> >
> > * [MJAR-178] - Change information on site
> > * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
> > * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter
> instead as a component.
> > * [MJAR-182] - Update version of plexus-archiver to 2.6.3
> > * [MJAR-184] - Update version of plexus-archiver to 2.7
> > * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
> > * [MJAR-187] - Upgrade maven-archiver to 2.6
> > * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
> > * [MJAR-191] - Upgrade to maven-plugins parent version 27
> >
> > Enjoy,
> >
> > - The Apache Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
> commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
AW: Release Notes in Plugin Sites
Posted by "Krull, Stephan" <St...@ecg-leipzig.de>.
I agree that there is no HUGE benefit to it. Just a matter of conformity to common practices.
When you start to release will the release notes from the JIRA version be finished? That way one could append the link of the release notes to the project overview page before the maven site generation for the release starts.
I would not vote for integrating the changes plugin if that leads to problems.
-----Ursprüngliche Nachricht-----
Von: Karl Heinz Marbaise [mailto:khmarbaise@gmx.de]
Gesendet: Dienstag, 10. März 2015 12:15
An: Maven Developers List
Betreff: Re: Release Notes in Plugin Sites
Hi Stephan,
the question on this is: What would be the benefit of this? Or in other
words: Will it bring supplemental information?
All the information is available as you already mentioned...if you really interested you can find the information....
Apart from that i could think of using maven-changes-plugin to handle this...which unfortunately would make the release process more fragile...and which would mean to change the configuration for all 49 plugins...(here on apache)...
To be honest: Is that really worth the effort...?
What do the other devs think?
Kind regards
Karl Heinz Marbaise
On 3/10/15 12:01 PM, Krull, Stephan wrote:
> Hello Maven folks,
>
> I wonder if there is a possibility to include release notes for plugin versions into the common maven site structure. the release notes are available via announcement email (i.e. attached mail) or via JIRA issue tracker from i.e. http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
>
> It would be helpful to have that information included in the standard maven site for an (official) plugin. Probably in a new section on the overview page (i.e. http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new menu entry under menu section "Project Information".
>
> What do you think?
>
> Kind regards
> Stephan Krull
>
>
> -----Ursprüngliche Nachricht-----
> Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
> Gesendet: Dienstag, 10. März 2015 11:38
> An: announce@maven.apache.org
> Cc: users@maven.apache.org; dev@maven.apache.org
> Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
>
> The Apache Maven team is pleased to announce the release of the Apache
> Maven Jar Plugin, version 2.6
>
> This plugin provides the capability to build jars.
>
> http://maven.apache.org/plugins/maven-jar-plugin/
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.6</version>
> </plugin>
>
> Release Notes - Maven JAR Plugin - Version 2.6
>
> Bugs:
>
> * [MJAR-135] - encoding problem with folder-names
> * [MJAR-151] - Error assembling JAR on OS X
> * [MJAR-179] - Adding empty files to jar failed with a ZipException : bad CRC checksum
> * [MJAR-185] - Update version of plexus-archiver to 2.7.1
> * [MJAR-188] - maven-jar-plugin is very slow on machines with slow Unix group lookups
> * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
>
> Improvements:
>
> * [MJAR-178] - Change information on site
> * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
> * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter instead as a component.
> * [MJAR-182] - Update version of plexus-archiver to 2.6.3
> * [MJAR-184] - Update version of plexus-archiver to 2.7
> * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
> * [MJAR-187] - Upgrade maven-archiver to 2.6
> * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
> * [MJAR-191] - Upgrade to maven-plugins parent version 27
>
> Enjoy,
>
> - The Apache Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Release Notes in Plugin Sites
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Stephan,
the question on this is: What would be the benefit of this? Or in other
words: Will it bring supplemental information?
All the information is available as you already mentioned...if you
really interested you can find the information....
Apart from that i could think of using maven-changes-plugin to handle
this...which unfortunately would make the release process more
fragile...and which would mean to change the configuration for all 49
plugins...(here on apache)...
To be honest: Is that really worth the effort...?
What do the other devs think?
Kind regards
Karl Heinz Marbaise
On 3/10/15 12:01 PM, Krull, Stephan wrote:
> Hello Maven folks,
>
> I wonder if there is a possibility to include release notes for plugin versions into the common maven site structure. the release notes are available via announcement email (i.e. attached mail) or via JIRA issue tracker from i.e. http://maven.apache.org/plugins/maven-jar-plugin/issue-tracking.html .
>
> It would be helpful to have that information included in the standard maven site for an (official) plugin. Probably in a new section on the overview page (i.e. http://maven.apache.org/plugins/maven-jar-plugin/index.html) or a new menu entry under menu section "Project Information".
>
> What do you think?
>
> Kind regards
> Stephan Krull
>
>
> -----Ursprüngliche Nachricht-----
> Von: Karl Heinz Marbaise [mailto:khmarbaise@apache.org]
> Gesendet: Dienstag, 10. März 2015 11:38
> An: announce@maven.apache.org
> Cc: users@maven.apache.org; dev@maven.apache.org
> Betreff: [ANN] Apache Maven Jar Plugin Version 2.6 Released
>
> The Apache Maven team is pleased to announce the release of the Apache Maven Jar Plugin, version 2.6
>
> This plugin provides the capability to build jars.
>
> http://maven.apache.org/plugins/maven-jar-plugin/
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jar-plugin</artifactId>
> <version>2.6</version>
> </plugin>
>
> Release Notes - Maven JAR Plugin - Version 2.6
>
> Bugs:
>
> * [MJAR-135] - encoding problem with folder-names
> * [MJAR-151] - Error assembling JAR on OS X
> * [MJAR-179] - Adding empty files to jar failed with a ZipException : bad CRC checksum
> * [MJAR-185] - Update version of plexus-archiver to 2.7.1
> * [MJAR-188] - maven-jar-plugin is very slow on machines with slow Unix group lookups
> * [MJAR-189] - Upgrade plexus-archiver dependency to v2.9
>
> Improvements:
>
> * [MJAR-178] - Change information on site
> * [MJAR-180] - Upgrade to Maven 2.2.1 compatiblity
> * [MJAR-181] - MavenProject/MavenSession Injection as a paremeter instead as a component.
> * [MJAR-182] - Update version of plexus-archiver to 2.6.3
> * [MJAR-184] - Update version of plexus-archiver to 2.7
> * [MJAR-186] - Upgrade maven-plugins-testing-harness from 1.2 to 1.3
> * [MJAR-187] - Upgrade maven-archiver to 2.6
> * [MJAR-190] - Upgrade to maven-plugins version 25 to 26
> * [MJAR-191] - Upgrade to maven-plugins parent version 27
>
> Enjoy,
>
> - The Apache Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org