Eclipse Community Forums: Rich Client Platform (RCP) » Pre-signing JARs for PDE WebStart build

Home » Eclipse Projects » Rich Client Platform (RCP) » Pre-signing JARs for PDE WebStart build

Pre-signing JARs for PDE WebStart build [message #449052]

Tue, 09 May 2006 12:04

Eclipse User

I use the automated PDE Build to build my application and deploy it via
WebStart. Everything works and I'm happy.

BUT...

The build takes nearly 15 minutes, and a very significant chunk of that is
signing the JARs. The biggest and most numerous JARs are the ones that are
in my Target Platform, and they don't change with every build.

So what I'd like to do is pre-sign all of the JARs in my Target Platform
(I can handle that bit) and then tell the PDE Build not to sign them again
(that's the bit I can't seem to do).

I can see two possible ways of controlling the behaviour I want:

1) Only sign JARs that have been built by the currently running build.
2) Only sign JARs that are not already signed.

One of these could be implemented as a boolean property, perhaps. What do
you think?

- Neil

Re: Pre-signing JARs for PDE WebStart build [message #449064 is a reply to message #449052]

Tue, 09 May 2006 21:14

Eclipse User

Have you verified what is happening if you are trying to sign a jar
already signed?

What you can try is:
- create a feature that only refer to the plugins you authored
- build this feature and sign it (make sure that runPackager=false)
- create a feature that includes the previous feature and the stuffs you
need from the target platform
- export the latter feature and create the jnlp file at this time, of
course turn signature off.

I have not tested this but it sounds like this should do it. Let me know
here.

PaScaL

Neil Bartlett wrote:
> I use the automated PDE Build to build my application and deploy it via
> WebStart. Everything works and I'm happy.
>
> BUT...
>
> The build takes nearly 15 minutes, and a very significant chunk of that
> is signing the JARs. The biggest and most numerous JARs are the ones
> that are in my Target Platform, and they don't change with every build.
>
> So what I'd like to do is pre-sign all of the JARs in my Target Platform
> (I can handle that bit) and then tell the PDE Build not to sign them
> again (that's the bit I can't seem to do).
>
> I can see two possible ways of controlling the behaviour I want:
>
> 1) Only sign JARs that have been built by the currently running build.
> 2) Only sign JARs that are not already signed.
>
> One of these could be implemented as a boolean property, perhaps. What
> do you think?
>
> - Neil
>

Previous Topic:	View Dropping
Next Topic:	[DataBinding] Dependency on ICU4J

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Aug 31 12:09:36 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter