Why don't you unzip/unjar your dependecy and use "normal" way of processing resources?
I am myself using zips as dependencies (type = "zip" ) - and I am unzipping them to folder like traget/resources Then I use <resources> section for selecting/filtering strings in those files. I created "zip-plugin" for that. This plugin which can unzips all zip dependecies and create new zip. There are still some things which are not working properly in everycase (e.g overrding of files may be sometimes desired, sometimes not) I am not working at the moment on the project which needs this functionality and I have no time for that now at work nor I have personal need to improve what I have wriiten. What I have is not fully tested and splitted into 2 plugins and some amevn.xml scripts but it works for me. If somebody is interested I may merge bits of the code into one plugin and commit new zip plugin to CVS. Zip plugin already might be quite useful in limited set of cases but the very technique of merging artifacts can be taken much further. I am using it for creating deployments containing jdk, couple wars, webserver (tomcat in my case), configuration files for tomcat, ghostscript etc. I am also using this technique for "customizing" artifacts - e.g. I have plugin which takes existing war and bunch of the configuration files and adds them all to a zip file ad installs this file in repository. Thanks to that I fro example able to create war files for different deployment nodes. I didn't need much time to implement such solution and it requires very little scripting - but I haven't yet been thinking how and if it can be generalized. Michal > -----Original Message----- > From: Carlos Sanchez [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 29, 2004 11:42 AM > To: 'Maven Developers List' > Subject: Maven extract plugin proposal > > > Hi, > > I need a way to extract resources from dependency artifacts, > and am thinking > about a "maven-extract-plugin". I post this to know if anyone > is working on > it and to get your comments. > > The best approach I see is to add a property to the > dependency with nested > resource tags as specified in pom build resources. > > <properties> > <extract> > <resource> > <directory/> > <targetPath/> > <includes> > <include/> > </includes> > <excludes> > <exclude/> > </excludes> > </resource> > </extract> > </properties> > > But I think the properties tag can't have nested ones, so a > workaround could > be: > > <properties> > <extract.directory/> <!-- default to root artifact directory --> > <extract.targetPath/> <!-- default to maven.build.dest --> > <extract.include/> <!-- one or more --> > <extract.exclude/> <!-- one or more --> > <!-- previous four tags can be repeated --> > </properties> > > > Feedback is greatly appreciated. > > > Regards > > Carlos Sanchez > A Coruņa, Spain > > Oness Project > http://oness.sourceforge.net > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
