o unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/-vote--Allowing-Ant-based-plugins-to-use-fi
Tentative +1...
There should be a metadata XML file that accompanies the build.xml file for
the plugin, which allows you to use normal mojo expressions to
declare/define parameters to be injected. I think you should be able to use
things like ${plugin} to get at the PluginDescriptor, and ${projec
On 6 Oct 06, at 8:24 PM 6 Oct 06, Kenney Westerhof wrote:
+1, and i'm really curious how you would fit that into 10 lines.. ;)
After I worked on Plexus Archiver it's now 12 lines :-)
Btw, IIRC the current ant plugin tools already unpack the jar to /
tmp/someplace
so they can specify the lo
+1, and i'm really curious how you would fit that into 10 lines.. ;)
Btw, IIRC the current ant plugin tools already unpack the jar to /tmp/someplace
so they can specify the location to the build.xml in the archive; I seem to
remember
that you couldn't just present an InputStream or URL to Ant to
+1 sounds interesting.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, October 06, 2006 6:33 PM
To: Maven Developers List
Subject: [vote] Allowing Ant-based plugins to use file-based resources
Hi,
I chatted with Kenney briefly about allowing ant-based
Hi,
I chatted with Kenney briefly about allowing ant-based plugins to
unpack resources from a known location to a known location so they
things like shell scripts can be executed.
So, in a nutshell I would like to add some capability to unpack the
resources in an ant-based plugin JAR to $
