[jira] (MPJNLP-29) Native library support?

["Michael Osipov (JIRA)" <ji...@codehaus.org>]

     [ https://jira.codehaus.org/browse/MPJNLP-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MPJNLP-29.
--------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Native library support?
> -----------------------
>
>                 Key: MPJNLP-29
>                 URL: https://jira.codehaus.org/browse/MPJNLP-29
>             Project: Maven 1.x JNLP Plugin
>          Issue Type: Bug
>         Environment: Ubuntu Linux, x86_64, ibm 150 jre.
>            Reporter: Andy Brook
>
> I havent seen any examples of how native libraries are supported.  My scenario is an SWT application that uses the SWT jar from eclipse, v3.1.1 now has the .so / .dll at the root of a JAR with java classes underneath.
> If it doesnt support this yet will it?  At the moment, the plugin does the lions share of signing, I just have to modify the template and hard code an additional <nativelib> tag.  It would be ideal If in addition to $dependencies in the velocity template, there was a $nativeDependencies.  This would then allow the SWT jar above to be referenced.
> I see there is some code relating to native library processing that is currently commented out.  What I would like to avoid is having to extract native libraries such that the plugin can resign them again, using SWT as the example, the jar has already been signed, I just need to refer to it as a native lib.
> One way is to extend the <dependencies> tag to have a natives section and in addition to specifying absolute libraries (.so / .dll ) for .jar wrapping/signing, the ideal would be to use the same descriptor as the <includes>  giving:
>     <dependencies>
>              <includes>
>                 <include>commons-logging:commons-logging</include>
>                 <include>commons-cli:commons-cli</include>
> 		<include>org.eclipse.core:boot</include>
>                 <include>org.eclipse.core:runtime</include>                
>                 <include>org.eclipse:swt</include>
>                 <include>org.eclipse.swt:win32-x86</include>
>                 <include>org.eclipse:jface</include>
>                 <include>org.eclipse.jface:text</include>
>                 <include>log4j:log4j</include>
>                 <include>myco:myapp</include>
>              </includes>
>              <!-- excludes>
>                 <exclude></exclude>
>              <excludes-->
>             <nativeIncludes>
>                 <include>org.eclipse.swt:win32-x86</include> <!-- this contains java classses and the native libraries -->
>             </nativeIncludes>
>        </dependencies>



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)