The only concern, would be that we need multiple Geronimo commiters with
commit and release access to the dependent Mojo project, so we don't lie
in limbo when we need fixes/changes made to the plugin to support new
build requirements
-Donald
Jason Dillon wrote:
Folks, I'm thinking
I agree with Donald because this code (plugins/plugin-support) is
very closely tied to geronimo. Here is an example:
System.getProperties().remove(geronimo.bootstrap.logging.enabled);
Thanks
Anita
--- Donald Woods [EMAIL PROTECTED] wrote:
The only concern, would be that we need multiple
On Feb 26, 2007, at 8:29 AM, Anita Kulshreshtha wrote:
I agree with Donald because this code (plugins/plugin-support) is
very closely tied to geronimo. Here is an example:
System.getProperties().remove(geronimo.bootstrap.logging.enabled);
This is the only bit from plugin-support that is
On Feb 26, 2007, at 7:08 AM, Donald Woods wrote:
The only concern, would be that we need multiple Geronimo commiters
with commit and release access to the dependent Mojo project, so we
don't lie in limbo when we need fixes/changes made to the plugin to
support new build requirements
On Feb 25, 2007, at 12:42 AM, Tomasz Pik wrote:
I would much rather see the Groovy stuff work the same way as the
Beanshell and Ruby mojos. What is the script-maven plugin exactly?
Some BSF thing?
The 'BSF thing' is here: http://mojo.codehaus.org/script-maven-plugin/
I'm using this with some
On 2/25/07, Jason van Zyl [EMAIL PROTECTED] wrote
On 24 Feb 07, at 8:22 PM 24 Feb 07, Jason Dillon wrote:
Folks, I'm thinking about moving the plugin-support module out of
Genesis and into the Mojo project. A few plugins I maintain there
already use some parts of this, but the classes were
On Feb 24, 2007, at 6:18 PM, Jason van Zyl wrote:
I still have some of the work I did to make richer Groovy plexus
components around too, which is to help make Mojo's with Groovy,
but I have not had time to deal with merging my bits into the bits
under Mojo's mojo-sandbox/groovy-maven-tools
Folks, I'm thinking about moving the plugin-support module out of
Genesis and into the Mojo project. A few plugins I maintain there
already use some parts of this, but the classes were simply duplicated.
I'm also planning on updating the groovy-maven-plugin at the Mojo
project to have the
On 24 Feb 07, at 8:22 PM 24 Feb 07, Jason Dillon wrote:
Folks, I'm thinking about moving the plugin-support module out of
Genesis and into the Mojo project. A few plugins I maintain there
already use some parts of this, but the classes were simply
duplicated.
I'm also planning on
On Feb 24, 2007, at 5:54 PM, Jason van Zyl wrote:
On 24 Feb 07, at 8:22 PM 24 Feb 07, Jason Dillon wrote:
Folks, I'm thinking about moving the plugin-support module out of
Genesis and into the Mojo project. A few plugins I maintain there
already use some parts of this, but the classes were
Here is a tiny example of the plugin actually doing something useful:
https://svn.apache.org/repos/asf/geronimo/sandbox/hokeypokey/
trunk/pom.xml
A tiny bit of logic here is used to prevent extra downloading/
unpacking. To make this into an official Maven plugin would be
overkill.
On 24 Feb 07, at 9:07 PM 24 Feb 07, Jason Dillon wrote:
On Feb 24, 2007, at 5:54 PM, Jason van Zyl wrote:
On 24 Feb 07, at 8:22 PM 24 Feb 07, Jason Dillon wrote:
Folks, I'm thinking about moving the plugin-support module out of
Genesis and into the Mojo project. A few plugins I maintain
On Feb 24, 2007, at 6:18 PM, Jason van Zyl wrote:
AFAIK, BSF-like execution isn't rich enough, unless I re-write the
engine to allow customizing the classpath/scriptpath, etc... and
even then I'm not sure it will cut it.
It's not. I'm not a fan of BSF and never used it in Plexus for
13 matches
Mail list logo
