Upgrade to latest Apache Parent pom...?

[Robert Burrell Donkin <ro...@blueyonder.co.uk>]

Rat currently inherits from an older version (9) of the Apache parent 
pom[1]. This inheritance supplies lots of suitable defaults. Unless 
anyone thinks this might be a poor plan, probably a good idea to upgrade 
to the latest version[2] before cutting the release.

Opinions?
Objections?

Robert
[1] http://maven.apache.org/pom/asf/
[2] 
http://svn.apache.org/viewvc/maven/pom/tags/apache-13/pom.xml?view=markup

Re: Upgrade to latest Apache Parent pom...?

[Robert Burrell Donkin <ro...@blueyonder.co.uk>]

On 03/11/13 18:46, sebb wrote:
> On 11 March 2013 11:51, Robert Burrell Donkin
> <ro...@blueyonder.co.uk> wrote:
>> Rat currently inherits from an older version (9) of the Apache parent
>> pom[1]. This inheritance supplies lots of suitable defaults. Unless anyone
>> thinks this might be a poor plan, probably a good idea to upgrade to the
>> latest version[2] before cutting the release.
>>
>> Opinions?
>
> The current version fixes the following:
>
> [MPOM-32] Apache POM 10 forces all child projects to generate the
> project info reports
>
> This was why Commons stuck to using version 9 until recently; perhaps
> RAT did too.
>
> Commons has now updated to the current version, and I've not seen
> reports of any problems.
>
> So I say go for it.

Committed :-)

I've regenerated the subsites[1][2], and they look okay to me. Please 
jump if anyone finds any issues (new or old ;-)...

Robert
[1] http://creadur.apache.org/whisker/
[2] http://creadur.apache.org/rat/

Re: Upgrade to latest Apache Parent pom...?

[sebb <se...@gmail.com>]

On 11 March 2013 11:51, Robert Burrell Donkin
<ro...@blueyonder.co.uk> wrote:
> Rat currently inherits from an older version (9) of the Apache parent
> pom[1]. This inheritance supplies lots of suitable defaults. Unless anyone
> thinks this might be a poor plan, probably a good idea to upgrade to the
> latest version[2] before cutting the release.
>
> Opinions?

The current version fixes the following:

[MPOM-32] Apache POM 10 forces all child projects to generate the
project info reports

This was why Commons stuck to using version 9 until recently; perhaps
RAT did too.

Commons has now updated to the current version, and I've not seen
reports of any problems.

So I say go for it.

> Objections?
>
> Robert
> [1] http://maven.apache.org/pom/asf/
> [2]
> http://svn.apache.org/viewvc/maven/pom/tags/apache-13/pom.xml?view=markup

Re: Upgrade to latest Apache Parent pom...?

[Robert Burrell Donkin <ro...@blueyonder.co.uk>]

On 03/11/13 23:17, sebb wrote:
> On 11 March 2013 21:05, P. Ottlinger <po...@aiki-it.de> wrote:
>> Hi,
>>
>> Am 11.03.2013 12:51, schrieb Robert Burrell Donkin:
>>> Opinions?
>>
>> +1
>> Go for it.
>>
>> Should we raise the version of Java as well?
>>
>
> No.
>
> That's completely different, as it affects end users directly.
> The version of Java should only be increased if necessary to support
> essential new features.
> Otherwise it just prevents the code from running on some user systems
> for no good reason.

For build tools like Apache Rat, I think that it's important to allow 
existing users to upgrade as easily as possible.

Robert

Re: Upgrade to latest Apache Parent pom...?

[sebb <se...@gmail.com>]

On 11 March 2013 21:05, P. Ottlinger <po...@aiki-it.de> wrote:
> Hi,
>
> Am 11.03.2013 12:51, schrieb Robert Burrell Donkin:
>> Opinions?
>
> +1
> Go for it.
>
> Should we raise the version of Java as well?
>

No.

That's completely different, as it affects end users directly.
The version of Java should only be increased if necessary to support
essential new features.
Otherwise it just prevents the code from running on some user systems
for no good reason.

Re: Upgrade to latest Apache Parent pom...?

["P. Ottlinger" <po...@aiki-it.de>]

Hi,

Am 11.03.2013 12:51, schrieb Robert Burrell Donkin:
> Opinions?

+1
Go for it.

Should we raise the version of Java as well?


Cheers
Philipp