> >
> > What I'm 'concerned' about is doing "mvn clean" at a much higher-level
> > (because of some other problem else where in the build-system, and thus
> > triggering an unnecessary signing later.
>
> the mvn clean you only need to run it in the module that uses the
> webstart plugin. How does that affect your build time so much ?
You're looking at it backwards (IMO). the webstart project is one of a dozen
projects. If I have problems else where in the build, I'm likely to try do
a "mvn clean install" at the top level. because the webstart project is one
of the twelve, it will have it's jars resigned (I'm OK with that for jars I'm
building, but I've got far more code in third-party jars than I do in any of
those twelve projects and they do not need to be signed again (generally)).
Maybe just having a seperate target (and maybe it's not the webstart plugin)
that would just sign dependent jars and put them in the repository. And the
webstart would just look for those signed jars before using pulling unsigned
one signing them itself.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
