[ http://jira.codehaus.org/browse/MWEBSTART-8?page=comments#action_83525 ] 
            
Jerome Lacoste commented on MWEBSTART-8:
----------------------------------------

Craig,

if I understand you, if you are able to add something like

<nativelibs>
  <nativelib>yourdep1</nativelib>
  <nativelib>yourdep2</nativelib>
</nativelibs>

in your POM then make sure something like 

#foreach($artifact in $config.packagedJnlpNativeArtifacts)
  <resources #if($jar.os) os="${jar.os}" #end>
    <nativelib href="${jar}"/>
  </resources>
#end

works in the velocity template, making sure that native artifacts are removed 
from the list of 'normal' artifacts (packagedJnlpArtifacts).

That would be sufficient right ?


> support native libraries
> ------------------------
>
>                 Key: MWEBSTART-8
>                 URL: http://jira.codehaus.org/browse/MWEBSTART-8
>             Project: Maven 2.x Webstart Plugin
>          Issue Type: New Feature
>            Reporter: Jerome Lacoste
>
> nativelib are resiyrces that are tagged in the following way in a jnlp file:
> <resources os="Windows">
>   <nativelib href="thedll.jar"/>
> </resources>
> To support nativelib at the same level of simplicity that the usual 
> dependencies are supported requires to:
> - automatically identify them from 
> - automatically wrap .dll .so files in jar files
> Q: what about jar files that are architecture dependent?
> In maven 1 it was possible to attach some properties to the dependencies. But 
> we cannot use that anymore.
> We could
> 1- mark the dependencies in the pom using the correct <type> in the pom. E.g. 
> <type>dll</type>
> 2- make the plugin automatically wrap the native dependency inside a jar.
> 3- automatically fill up the <nativelib> elements using some sort of filter 
> mecanism
> <resources os="Windows">
>   $allDependencies.filter("dll")
> </resources>
> ??
> $dependencies would implicitly map to $allDependencies.filter("jar") for 
> backward compatibility.
> Better: the filter() argument might be a JDK 1.4 regex matching a dependency 
> notation. That way we solve the architecture  issue (we can match names, 
> types, etc..)
> That's just one idea. We can perhaps do better? Let me know how you see it.

-- 
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 from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to