Is that anything that "assembly:single"[1] might help with? I'm not overly expectant, but just wanted to check you'd seen it?
Failing that, how feasible would it be to tie things together with a custome script? Ant, sh, python/jython, etc... /Gwyn [1] http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html On 22/03/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
The whole maven stack: each life cycle doesn't check if the required artifacts are already available. The only reason it doesn't recompile is because the java compiler itself is clever enough to notice no changes between the source and classes directory. Everything else is done again, and again and again and again and again. Where everything else is: generate javadoc, create source jar,, javadoc jar, classes jar, sign them, upload them to the repo. If you add a site generation to the mix, you'll have to generate the javadoc twice, and if you have a unit test report, those will run again too. This is the reason why building a release takes a day. Martijn On 3/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > sounds like the assembly plugin needs to be fixed. > > -igor > > > On 3/21/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > 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
-- Download Wicket 1.2.5 now! - http://wicketframework.org
