Hi,
Changes in v3:
Change the legal-bundle to have really simple NOTICE file and put all
the dependency info in a separate DEPENDENCIES file. This
corresponds to what appears to be current thinking on legal-discuss
about what should be in these files. We should be able to use this
bundle with the maven-remote-resources-plugin everywhere now.
Fiddle around with the maven site generation and site deployment so
it more or less works. Add some instructions in the project-config
site.
Changes in v2:
Change in the release plugin configuration to use the default tagBase
in release profiles in projects that inherit from the project-config
pom. It is also possible to override tagBase but this should not be
necessary as we adhere to standard svn layout. There are also some
plugin version upgrades.
The new root pom includes a release profile that sets up the standard
javadoc, source and gpg plugins and uses the default tagBase location.
This sets us up for using the release process also now under vote
described at http://cwiki.apache.org/confluence/display/GMOxPMGT/
Proposed+%28updated%29+release+process
The only Jira I know about is https://issues.apache.org/jira/browse/
GERONIMO-3895
Staging repo:
http://people.apache.org/~djencks/staging-repo/org/apache/geronimo/
genesis/
site staging:
http://people.apache.org/~djencks/staging-site/maven/genesis/1.4/
This time I was able to use mvn site site-deploy -Prelease,default to
deploy the site all at once to the staging-site.
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
thanks
david jencks
