David Jencks wrote:
Stuff is piling up that we (or at least I) would like in the portals-pom
- ianal plugin on all builds
- better name for prepare-release profile if it really cant be
apache-release
- corrected organization name
- assembly plugin configuration for source distros.
what if we released a portals-pom 1.2 and spec jars in the same vote?
We've done multiple-source/artifact releases pretty often in geronimo.
OK, I'm fine with that too as it won't cause further delays.
thanks
david jencks
On May 11, 2009, at 3:30 PM, Ate Douma wrote:
Carsten Ziegeler wrote:
Sorry for the late response, but I just noticed that we have a typo in
the pom. The organization needs to be "The Apache Software Foundation" -
this is our official name.
Sigh
The problem with this is that this value is picked up by some maven
plugins like the maven bundle plugin which we use for the portlet api's.
We can solve this by overwriting the value in the spec poms.
+1
Can we just do so for the spec poms and *not* hold up the release yet
another 3 days?
Nevertheless I think we should just do another release.
I'm fine with doing another portals-pom-1.2 tomorrow so the upcoming
releases for APA, Pluto and Jetspeed-2 can leverage that.
But as the *formal* release of an ASF project constitutes the *src*
distribution, we can (by overriding the organization name in the spec
poms) still produce valid ASF releases for these spec projects,
*without* needing to wait upon the portals-pom-1.2, agreed?
Regards,
Ate
Regards
Carsten
