Guys, I've almost given up on using maven for building a consistent release, which is also properly signed.
Themain problem I run into: Maven insists to rebuild/repackage everything on each invocation, which invalidates any signature generated in an earlier invocation. This is problematic because we need to build our JDK-1.4 branch using JDK-1.4 and the rest using JDK-1.5 I am able to create the jars and deploy them to my repository, signed and all using JDK-1.4. No problem. Same goes for the JDK-1.5 projects. I just can't run mvn assembly:assembly when the deploy has finished, becuase it will create new jar files (even though they are already there!) and thus invalidate any signature. The only way out I see is to compile using JDK-1.4, and package/assemble using JDK-1.5. Given that this is a legal only release, I'll do that now, and we'll see how it stands up to the tests. 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
