On 3/22/07, Gwyn Evans <[EMAIL PROTECTED]> wrote:
Is that anything that "assembly:single"[1] might help with? I'm not overly expectant, but just wanted to check you'd seen it?
I tried to do a mvn deploy assembly:assembly before I went to bed last night, but it only performed the dark arts on the JDK-1.4 profile (the mvn runs using jdk-1.5, and should default to the all profile). So my current setup would be: mvn4 deploy -Dgpg.passphrase=foobar mvn deploy -Dgpg.passphrase=foobar mvn package assembly:assembly Problem is that the package phase of the last command recreates all jars, thus invalidating the signatures. I'm not alone with this problem (I mailed the [EMAIL PROTECTED] list), so I have to search for an alternative. One could be: mvn4 package mvn package mvn deploy assembly:assembly -Dgpg.passphrase=foobar which creates the jar files using JDK-1.5 jar, instead of JDK-1.4 jar, but I don't think *that* would constitute a problem. This is the last thing I tried to perform before going to bed, but it didn't do the java 1.5 projects. I'll start it up one last time and if that fails, we should look for alternatives.
Failing that, how feasible would it be to tie things together with a custome script? Ant, sh, python/jython, etc...
Problem is the dependency resolving. The current module set in the maven assembly discovers and includes the spring, junit, logging etc. libraries. If we don't want to ship those, things are looking better. Then it would be an Ant zip target to create the distribution. Part of the appeal of a binary distribution is that you can start working with the set and don't have to go on a dependency hunt. Martijn -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org
