On Oct 12, 2006, at 8:15 AM, John Casey wrote:
1. I don't think anyone can complain with compliance issues. One
thing I
would say is, we could/should be using a plugin to resolve the
license file
from the url given in the POM, and include it in the appropriate
place. Not
only would this ensure that the license is properly included in the
binary,
but also that it's accessible separately, which IMO is a good
thing. This
doesn't require new core functionality, just a new plugin.
Unfortunately this does not include any notice txt that might also
need to be included. Geronimo uses a mojo to copy this files to
avoid the issues with eclipse:
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/tools-
maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/tools/
CopyLegalFilesMojo.java
3. I think we have some code in commons-* somewhere to do pgp
signing, but I
don't think it's finished yet. If we could get this done, we could
easily
write a plugin to do this during the release process, I think.
I wrote a trivial gpg mojo a month ago or so, which signs everything
and attaches the sigs to be installed, so deploy handles artifact and
signature uploads:
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/tools-
maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/tools/
GpgSignAttachedMojo.java
Its not perfect, but it works.
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
