[ http://jira.codehaus.org/browse/MASSEMBLY-66?page=comments#action_61891 ] 

ruel loehr commented on MASSEMBLY-66:
-------------------------------------

Essentially, you need to have zipfileset support.   This could be very useful . 
  On the maven site, this wouldn't be so tough too add, but plexus utils would 
need to be modified to have a zipfilescanner.

> Ability to index into a nominated dependency JAR to identify files to include 
> in the assembly (Im thinking .so/.dll etc)
> ------------------------------------------------------------------------------------------------------------------------
>
>          Key: MASSEMBLY-66
>          URL: http://jira.codehaus.org/browse/MASSEMBLY-66
>      Project: Maven 2.x Assembly Plugin
>         Type: Improvement

>  Environment: Linux, x86_64, x86, win32
>     Reporter: Andy Brook
>     Priority: Critical

>
>
> Im trying to bundle a SWT application, I'm almost there, the only thing 
> missing is the ability to include .so files in the assembly that are 
> currently stored inside a dependancy.  As far as I can tell there is no neat 
> way to pull a few files out of a given dependency...
> My example is the SWT libraries, the GTK linux specific JAR in the eclipse 
> bundle also contain the native libraries.  Ive renamed this to fit into a 
> maven2 repository, but really dont want to have to copy the files manually.
> Ideally, I would like to be able to specify the dependency in mind and extend 
> the fileSet element to allow the context of the include to work only within 
> that dependency.
> If there is something Im missing and this can be done with existing plugins 
> Id like to hear about it!
> eg:
> ::POM::
>     <!--ECLIPSE SWT GTK-->   
>     <dependency>
>       <groupId>org.eclipse.swt</groupId>
>       <artifactId>gtk-linux-x86</artifactId>
>       <version>3.1.1</version>
>       <scope>runtime</scope>
>     </dependency>
> ::assembly-descriptor.xml::
>     <!-- /native -->
>       <fileSet>
>       <dependency>org.eclipse.swt:gtk-linux-x86:3.1.1</dependency>
>       <outputDirectory>/lib</outputDirectory>
>       <includes>
>               <include>*.so</include>
>       </includes>
>     </fileSet>                

-- 
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

Reply via email to