directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot>
Subject Re: Project POM: 'release' profile, RAT check, altDeploymentRepository
Date Wed, 09 Feb 2011 12:14:33 GMT
Hi Stefan,

On 9 févr. 2011, at 12:28, 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.


> 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?

Seems fine to me.
But AFAIR, I think we disabled it because it was giving us false reporting of too many un-licensed
files and was preventing us from releasing because of that.
+1 for giving it another try.

> At last, we can remove the 'altDeploymentRepository' property which
> isn't used any more.



> Thoughts?
> Kind Regards,
> Stefan
> [1]

View raw message