On May 11, 2009, at 4:11 PM, David Sean Taylor wrote:
On May 11, 2009, at 3:59 PM, David Jencks wrote:
Stuff is piling up that we (or at least I) would like in the
portals-pom
- ianal plugin on all builds
what is that?
It checks that the apache-required legal files are present in every
artifact. It doesn't seem to happen with the apache-release profile
but often the legal files don't get into source and javadoc jars to
this is really pretty handy.
- 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.
thats a great idea. what if we voted on the pluto release at this
time as well ?
I looked at pluto trunk and think it will be a couple days before it's
ready to vote on. I don't see any problem in having overlapping
dependent votes however, e.g. pluto release depends on spec release
passing.
thanks
david jencks