On 4/13/07, David Corbin <[EMAIL PROTECTED]> wrote:
> >
> > 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.
Yes but there are two different problems:
- the fact that the skip sign incorrectly skips unsigned plugins after a mistake
- the fact that you want to avoid resigning jars. I know some people
moved the signing out of the webstart process, probably to solve that
issue. You can do so with the jar-signer mojo. Maybe that's what you
should look at. Then we will need a way to say: sign those jars, not
the others.
One way to do it would be to use a small signing application that sits
in front of a maven repository.
Look at
http://jira.codehaus.org/browse/MWEBSTART-18
http://jira.codehaus.org/browse/MJAR-35
and
the attached file:
http://jira.codehaus.org/secure/attachment/20090/lehmanjarsigner-1.0-src.zip
It might be interesting to talk to users to see if they would be
interested in implementing such a service in an open way.
Cheers,
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
