directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Lecharny <elecha...@gmail.com>
Subject Re: Project POM: 'release' profile, RAT check, altDeploymentRepository
Date Wed, 09 Feb 2011 12:09:18 GMT
On 2/9/11 12:28 PM, Stefan Seelmann wrote:
> Hi dev,
>
> while preparing the JUnit Add-ons release I noticed that the parent
> POM contains stuff which is IMHO outdated:
>
> There is a 'release' profile. In outdated release documentation [1]
> this profile is used. In the recent releases I didn't used the
> 'release' profile, so be default the 'apache-release' profile from the
> org.apache:apache:8 POM is used. The plugins configurations of
> maven-javadoc-plugin, maven-deploy-plugin, maven-gpg-plugin and
> maven-source-plugin are identical in both profiles. The
> org.apache:apache:8 POM configures an additional source-release
> assembly. Our project POM contains the RAT plugin but that is
> disabled. I'd propose to remove the 'release' profile because it just
> duplicates the 'apache-release' profile.

+1. We added our own release profile back in a time where the Maven 
parent pom didnt contain a apache-release profile, or it was buggy.

Now, it does not make sense to have our own.
> If we want to activate the RAT check we should instead extend the
> 'apache-release' profile and add the RAT plugin configuration there.
> Do we?
yes. RAT is part of the check we must do.

Thanks Stefan

-- 
Regards,
Cordialement,
Emmanuel L├ęcharny
www.iktek.com


Mime
View raw message