| PDE Build Bug with jar signing for eclipse folder plugins? [message #25704] |
Tue, 07 October 2008 16:27  |
Eclipse User |
|
|
|
Hey Guys,
So while using eclipse pde-build we noted a possible bug. If we
are building for web start deployment, and we specify to output jars,
build process creates a jar for any plugins in folder format (eg.
org.eclipse.core.runtime.compatibility.registry_3.2.100.v200 70316 in
Version: 3.3.2 Build id: M20080221-1800). Although that seems fine but
it messes up the jar signature somehow and running a jarSigner -verify
fails on the resultant jar causing webstart launch to fail as well.
Any idea whats the workaround and if this is a bug?
Thanks,
abhi
|
|
|
| Re: PDE Build Bug with jar signing for eclipse folder plugins? [message #25850 is a reply to message #25704] |
Wed, 08 October 2008 11:47  |
| Eclipse User |
|
|
|
This sounds like
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196754 which was fixed in 3.4
As for a workaround, the only thing I can think of would be to remove
the bad signature.
PDE/Build can "unsign" a jar before signing it. This was in case of
webstart not supporting jars containing more than one signature (yours &
the eclipse.org signature). This gets turned on automatically when
generating JNLP. You should also be able to turn it on by setting
"jarProcessor.unsign = true".
If you don't want the jars signed, but do want them unsigned, you would
need to set sign=true and jarProcessor.sign = false
-Andrew
Abhishek Misra wrote:
> Hey Guys,
> So while using eclipse pde-build we noted a possible bug. If we
> are building for web start deployment, and we specify to output jars,
> build process creates a jar for any plugins in folder format (eg.
> org.eclipse.core.runtime.compatibility.registry_3.2.100.v200 70316 in
> Version: 3.3.2 Build id: M20080221-1800). Although that seems fine but
> it messes up the jar signature somehow and running a jarSigner -verify
> fails on the resultant jar causing webstart launch to fail as well.
>
> Any idea whats the workaround and if this is a bug?
>
>
> Thanks,
> abhi
|
|
|
| Re: PDE Build Bug with jar signing for eclipse folder plugins? [message #582488 is a reply to message #25704] |
Wed, 08 October 2008 11:47 |
| Eclipse User |
|
|
|
This sounds like
https://bugs.eclipse.org/bugs/show_bug.cgi?id=196754 which was fixed in 3.4
As for a workaround, the only thing I can think of would be to remove
the bad signature.
PDE/Build can "unsign" a jar before signing it. This was in case of
webstart not supporting jars containing more than one signature (yours &
the eclipse.org signature). This gets turned on automatically when
generating JNLP. You should also be able to turn it on by setting
"jarProcessor.unsign = true".
If you don't want the jars signed, but do want them unsigned, you would
need to set sign=true and jarProcessor.sign = false
-Andrew
Abhishek Misra wrote:
> Hey Guys,
> So while using eclipse pde-build we noted a possible bug. If we
> are building for web start deployment, and we specify to output jars,
> build process creates a jar for any plugins in folder format (eg.
> org.eclipse.core.runtime.compatibility.registry_3.2.100.v200 70316 in
> Version: 3.3.2 Build id: M20080221-1800). Although that seems fine but
> it messes up the jar signature somehow and running a jarSigner -verify
> fails on the resultant jar causing webstart launch to fail as well.
>
> Any idea whats the workaround and if this is a bug?
>
>
> Thanks,
> abhi
|
|
|
Powered by
FUDForum. Page generated in 0.03755 seconds
Home