[ http://jira.codehaus.org/browse/MPJNLP-20?page=comments#action_38991 ]
     
Emil A. Lefkof III commented on MPJNLP-20:
------------------------------------------

I also have this issue where I need the manifest.mf to not be modified.  This 
fix is perfect.

> 'Update Manifest' feature should be optional
> --------------------------------------------
>
>          Key: MPJNLP-20
>          URL: http://jira.codehaus.org/browse/MPJNLP-20
>      Project: maven-jnlp-plugin
>         Type: Improvement
>  Environment: Mac OS X, Java 1.4.2
>     Reporter: M. Sean Gilligan
>     Assignee: Emmanuel Venisse
>      Fix For: 1.4.1
>  Attachments: maven-jnlp-plugin.diff
>
> Original Estimate: 1 hour
>         Remaining: 1 hour
>
> The maven-jnlp-plugin strips out all JAR manifest attributes and replaces 
> them with a bare-bones manifest that looks like this:
> Created-By: Apache Maven
> Manifest-Version: 1.0
> (Plus the SHA1-Digest attributes for each .class entry)
> Apparently this was to work around bugs in Java Web Start in the 1.3.x 
> versions of Java.  My App requires 1.4.x, so I created a patched version of 
> maven-jnlp-plugin that adds a property called 'maven.jnlp.update.manifest' 
> which defaults to 'true' for backward compatibility.
> Setting maven.jnlp.update.manifest=false will preserve attributes in the 
> signed JNLP JARs and seems to work fine with JWS in Java 1.4.2.
> I'm hoping someone will commit the patch and make a 1.4.2 release of the 
> plugin...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to