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 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
parse a build.xml.
Yah, this is in the AntScriptInvoker which is cool. But I need a
modification so that resources are unpacked before the build.xml file
is executed. So I'm making an addition to the AntMojoWrapper but I
need to add a few things:
1) the plugin JAR from the repository
2) the plugin id
3) the MavenProject so I can get the target directory
I was hoping I could get these from the plugin context, which is just
a Map, but there's nothing in there. So I can populate it in the
DefautPluginManager which is what I would like to do. John, is there
any other way to push values in the plugin context. I see the code in
the ReactorManager, and MavenSession but I'm not sure how you have
been using the context.
Anyway, I would like to make this change in the trunk and then in
branch as I don't think this is a huge change and highly useful.
If this is the case, you may want to re-use that unpack location
instead of copying
to target/.../.
But you probably know the code better than me :)
Jason van Zyl wrote:
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 ${basedir}/target/
<artifact-id> and from there if the ant scripts want to reference
file based resources they can. My particular use case is a user
that wants to leverage all the bash and perl they have already use
with their ant builds but they want them to be reusable.
If no one objects I'll do the work on trunk and then merge it to
the branch. It's a new feature but it's super simple (10 lines)
and it would certainly be useful in 2.0.5.
Jason
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
