Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of khmarbaise@gmx.de designates
 212.227.17.20 as permitted sender)
Message-ID: <54FEED74.6040708@gmx.de>
Date: Tue, 10 Mar 2015 14:11:16 +0100
From: Karl Heinz Marbaise <khmarbaise@gmx.de>
Reply-To: info@soebes.de
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Krull, Stephan" <Stephan.Krull@ecg-leipzig.de>,
 'Maven Developers List' <dev@maven.apache.org>,
 "'info@soebes.de'" <info@soebes.de>
Subject: Re: AW: Release Notes in Plugin Sites
References: <44BC0537546E8A4B8004C492661336C195E1971E@SVNG114.vngag.de>
 <54FED246.7050401@gmx.de>
 <44BC0537546E8A4B8004C492661336C195E198CC@SVNG114.vngag.de>
In-Reply-To: <44BC0537546E8A4B8004C492661336C195E198CC@SVNG114.vngag.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

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