I played with this a bit while working on the portlet-api poms. It
works pretty well however I have some reservations:
1. There is no compiler plugin source level specified. So, if you
have code beyond java 1.3, you need to configure the compiler plugin
in your pom. I think that portals is all on java 5 and maybe this
could be set in the portals-pom directly.
2. I don't like the name prepare-release for the profile that uses
ianal and rat. First, it doesn't actually prepare anything and is
confusingly similar to the release plugin release:prepare goal.
Second and more important I think the ianal pllugin should run by
default always. Alternatively the apache-release profile could
perhaps be extended to include these plugins.
Also, I suspect there will be an apache 7 pom soon as some work to
make the release plugin produce a source distribution more
automatically are underway. So it might be worth waiting another
couple days to see if this happens.
However these are fairly minor quibbles and we could postpone them.
thanks
david jencks
On May 8, 2009, at 5:12 AM, Vivek Kumar wrote:
Hi all
This new pom now uses the Apache 6 pom as parent which allowed to
cleanup and remove many elements.
Furthermore, the Portals developers info has been taken out to be
moved to a new main portals-site-pom shortly.
That will make it easier to incorporate updates to the developers
info without having to change this Portals super pom and thereby
effecting all sub projects and their versions.
Please review the release candidate POM from the Nexus staging
repository below:
https://repository.apache.org/content/repositories/portals-staging-014/org/apache/portals/portals-pom/1.1/
Please vote on releasing portals-pom-1.1 .
Vote is open for the next 72 hours.
Please cast your vote:
[ ] +1 for Release
[ ] 0 for Don't care
[ ] -1 Don't release, reason
Regards
Vivek Kumar
