On 2 March 2012 17:41, sebb <seb...@gmail.com> wrote:
> On 2 March 2012 10:50, Gilles Sadowski <gil...@harfang.homelinux.org> wrote:
>> Hello.
>>
>>> could we make the following additions to the release notes?
>>> New features
>>> MATH-655: framework for iterative linear solvers. Implementation of
>>> two solvers: conjugate gradient, SYMMLQ.
>>>
>>> Changes
>>> MATH-677, MATH-743: several changes to the API in the transform package.
>>>
>>
>> It seems that
>>
>> 1. The file "RELEASE-NOTES.txt" in trunk has not changed for release 2.2
>> 2. It was generated automatically (or it should anyways).
>
> The command to generate the release notes is:
>
> mvn changes:announcement-generate [-Dchanges.version=3.0]
>
> The version can be provided as shown to override the version in the POM.
>
>>
>> There is a note in the "UsingNexus" document:
>> ---CUT---
>> Ensure that the release notes refer to the release version, not snapshot. If
>> using automatic release note generation from changes.xml, the following
>> command should update the file:
>>
>> mvn changes:changes-report changes:announcement-generate
>>
>> The file generated is target/announcement/announcement.vm
>> ---CUT---
>>
>> But it does not work here. The output of
>>
>> $ mvn changes:changes-report
>>
>> is
>> ---CUT---
>> INFO] Scanning for projects...
>> [INFO]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Commons Math 3.0
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO]
>> [INFO] --- maven-changes-plugin:2.6:changes-report (default-cli) @
>> commons-math3 ---
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2.467s
>> [INFO] Finished at: Fri Mar 02 11:35:50 CET 2012
>> [INFO] Final Memory: 19M/174M
>> [INFO]
>> ------------------------------------------------------------------------
>> ---CUT---
>>
>> It looks nice... but does not change any file!
>>
>> The output of
>>
>> $ mvn changes:announcement-generate
>>
>> is
>> ---CUT---
>> [INFO] Scanning for projects...
>> [INFO]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building Commons Math 3.0
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO]
>> [INFO] --- maven-changes-plugin:2.6:announcement-generate (default-cli) @
>> commons-math3 ---
>> [WARNING] changes.xml file
>> /home/eran/devel/SVN/commons-math/trunk/src/changes/changes.xml does not
>> exist.
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 2.466s
>> [INFO] Finished at: Fri Mar 02 11:37:23 CET 2012
>> [INFO] Final Memory: 19M/174M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-changes-plugin:2.6:announcement-generate
>> (default-cli) on project commons-math3: No releases found in any of the
>> configured issue management systems. -> [Help 1]
>> [...]
>> ---CUT---
>>
>> It misses a file, so I deduce that this plugin is not used for the "math"
>> component; unfortunately there is no reference as to what might replace it.
>> :-{
>>
>> There is indeed a "changes.xml" file, but it is located in "src/site/xdoc".
>>
>> Since it is processed as part of the "site" plugin, I thought/imagined/hoped
>> that it would also generate what is referred to as "release notes"...
>
> The command:
>
> mvn changes:announcement-generate
>
> works for me.
>
> However, the file is not in the standard place (nor does it have the
> standard name) as expected by commons-parent.
Fixed.
Also updated the VM file so it no longer generates LF-only EOLs on
Windows for multiline changes paragraphs.
>>
>> Regards,
>> Gilles
>>
>> P.S. Sébastien,
>>
>> What you could do anyway is add a section in the "NOTICE.txt" file
>> about the original code/algorithm.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
