Provide unsigned jar as part of the distribution

[GoogleCodeExporter]

Provide an unsigned jar as part of the distribution so that applications
can sign the jar as required and not rely on the expiration date set in the
prebuilt jar (currently around September 2008).

Original issue reported on code.google.com by kirill.grouchnikov@gmail.com on 24 Jun 2008 at 3:56

[GoogleCodeExporter]

This may sound silly, but how do I do that?  I did not even know the jar was 
signed
:-).  Could be because the NetBeans jnlp build thing?

Original comment by ayman.al...@gmail.com on 24 Jun 2008 at 4:55

• Changed state: Accepted

[GoogleCodeExporter]

The simplest Ant task for creating a jar is:

<jar compress="true" destfile="...">
    <fileset ... />
</jar>

NB might indeed sign the jar by default, but it would be very inconvenient for 
the
users that use this jar in their own signed apps. To use a jar signed by another
party you need to split your JNLP into multiple files, and then depend on the 
owner
of the original jar (yourself) to keep resigning the jar every once in a while.

Thanks
Kirill

Original comment by kirill.grouchnikov@gmail.com on 26 Jun 2008 at 9:43

[GoogleCodeExporter]

Working on this for the next release, due out in just a few days.  

Original comment by ayman.al...@gmail.com on 28 Jun 2008 at 11:48

[GoogleCodeExporter]

I uploaded the unsigned JAR for the latest version.  Source is now on The 
Source Tab
using SVN.

Original comment by ayman.al...@gmail.com on 29 Jun 2008 at 9:27

• Changed state: Fixed