On Mar 27, 2007, at 4:50 PM, Filip Hanik - Dev Lists wrote:
I don't expect that Tomcat will switch to m2, though if they are
gonna be publishing m2 repos they should use the m2 antlib for
that. But, looks like the m2 antlib is not up to snuff wrt the
new? apache requirements to publish .asc files for releases. I
think the antlib tasks probably need to be updated to allow extra
files to be attached when install/deploying and then ant folks
should be sorted... well, that and if they implement a task or
macro to sign stuff.
we're note even using the antlibs, they were not really working
out. It was easier to just exec the mvn script directly. If Maven
has the command line option to do what we want, then we can do it.
Just curious, what wasn't working out with the antlibs? They should
prolly be fixed if they are not usable by ant projects.
So if you show me the "$MAVEN_HOME/bin/mvn" command to publish a
single JAR(with a POM) and being able to make sure the signature
goes with it, then we are fine.
GPG signing is a no brainer, we can do that any day.
Hrm... I'm not sure there exists such a command at the moment, though
its probably easy enough to craft a simple goal to implement what you
need.
The reason it doesn't work asis, is that the gpg .asc stuff is
attached to the current projects artifact and the install/deploy will
handle the primary artifact and then any attached artifacts
separately. The install-file/deploy-file goals don't have a project
to work on so there is nothing to attach to.
I suppose that either install-file/deploy-file need to take an
additional csv list of other files to "attach" or perhaps simply
craft a pom.xml which uses build-helper:attach-artifact ( http://
mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-
mojo.html ) and dance around mvn a little to make `mvn deploy` work.
But, it would really be better IMO, to use the <deploy> task and
update the task to have a nested set of <attached-file> elements
which can be used to effectively behave the same as mvn would
normally by deploying the primary artifact, and then any attached
artifacts. Thats *much* less of a hack.
Can you tell me why the antlib tasks aren't working for you?
--jason
