You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Eric Miles <er...@kronos.com> on 2008/03/12 21:23:39 UTC
plugin dependencies question
All,
I have a plugin I wrote, that use framework FooBar. This plugin will
work with FooBar version 1.1 through 1.8. I have numerous maven
projects that use my plugin and all use different versions of FooBar.
The version of FooBar is important to each project as compilation is
performed (compiled units are not backwards compatible). Is there a way
to create my plugin so that it uses FooBar for compilation, however the
individual projects specify which version of FooBar to the plugin via
the pom?
Thanks in advance,
Eric Miles
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin dependencies question
Posted by Wayne Fay <wa...@gmail.com>.
Alternatively, write your plugin such that it can use any version 1.1
through 1.8 and specify the version with a configuration element. Your
plugin will need a bit more intelligence to pull this off.
Wayne
On 3/12/08, Wayne Fay <wa...@gmail.com> wrote:
> One immediate thought: make a version of your plugin that corresponds
> with each version of FooBar.
>
> FooBar 1.1 => foobar-maven-plugin v1.1.0 (bug fixes will bump the .0)
> FooBar 1.2 => foobar-maven-plugin v1.2.0
> etc
>
> Then in your pom, lock down the foobar-m-p version with
> <version>[1.2]</version>.
>
> Wayne
>
> On 3/12/08, Eric Miles <er...@kronos.com> wrote:
> > All,
> >
> > I have a plugin I wrote, that use framework FooBar. This plugin will
> > work with FooBar version 1.1 through 1.8. I have numerous maven
> > projects that use my plugin and all use different versions of FooBar.
> > The version of FooBar is important to each project as compilation is
> > performed (compiled units are not backwards compatible). Is there a way
> > to create my plugin so that it uses FooBar for compilation, however the
> > individual projects specify which version of FooBar to the plugin via
> > the pom?
> >
> > Thanks in advance,
> > Eric Miles
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin dependencies question
Posted by Wayne Fay <wa...@gmail.com>.
One immediate thought: make a version of your plugin that corresponds
with each version of FooBar.
FooBar 1.1 => foobar-maven-plugin v1.1.0 (bug fixes will bump the .0)
FooBar 1.2 => foobar-maven-plugin v1.2.0
etc
Then in your pom, lock down the foobar-m-p version with
<version>[1.2]</version>.
Wayne
On 3/12/08, Eric Miles <er...@kronos.com> wrote:
> All,
>
> I have a plugin I wrote, that use framework FooBar. This plugin will
> work with FooBar version 1.1 through 1.8. I have numerous maven
> projects that use my plugin and all use different versions of FooBar.
> The version of FooBar is important to each project as compilation is
> performed (compiled units are not backwards compatible). Is there a way
> to create my plugin so that it uses FooBar for compilation, however the
> individual projects specify which version of FooBar to the plugin via
> the pom?
>
> Thanks in advance,
> Eric Miles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin dependencies question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
The RC will probably go out tomorrow. I planned on today, but I ran into
issues with the integration tests and I had to stop and setup some CI.
-----Original Message-----
From: Eric Miles [mailto:eric.miles@kronos.com]
Sent: Wednesday, March 12, 2008 8:55 PM
To: Maven Users List
Subject: RE: plugin dependencies question
I see there's only 5 issues outstanding left for 2.0.9. Does anyone
know when the expected release date is?
Thanks so much!
On Wed, 2008-03-12 at 19:22 -0400, Brian E. Fox wrote:
> Handy, isn't it?
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Wednesday, March 12, 2008 7:18 PM
> To: Maven Users List
> Subject: Re: plugin dependencies question
>
> That's new in 2.0.9. Well, not new, but now it works. ;-)
>
> Wayne
>
> On 3/12/08, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Yes. Compile against foobar normally. The users can specify the
> > dependency they want in the plugin configuration block. This is
> working
> > in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
> > http://jira.codehaus.org/browse/MNG-2972 for more information.
> >
> > In this way you can say your plugin will use FooBar version x.y by
> > default, but if they want to use another one, they can do so by
> > overriding it in their pom.
> >
> > -----Original Message-----
> > From: Eric Miles [mailto:eric.miles@kronos.com]
> > Sent: Wednesday, March 12, 2008 4:24 PM
> > To: users@maven.apache.org
> > Subject: plugin dependencies question
> >
> > All,
> >
> > I have a plugin I wrote, that use framework FooBar. This plugin
will
> > work with FooBar version 1.1 through 1.8. I have numerous maven
> > projects that use my plugin and all use different versions of
FooBar.
> > The version of FooBar is important to each project as compilation is
> > performed (compiled units are not backwards compatible). Is there a
> way
> > to create my plugin so that it uses FooBar for compilation, however
> the
> > individual projects specify which version of FooBar to the plugin
via
> > the pom?
> >
> > Thanks in advance,
> > Eric Miles
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin dependencies question
Posted by Eric Miles <er...@kronos.com>.
I see there's only 5 issues outstanding left for 2.0.9. Does anyone
know when the expected release date is?
Thanks so much!
On Wed, 2008-03-12 at 19:22 -0400, Brian E. Fox wrote:
> Handy, isn't it?
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Wednesday, March 12, 2008 7:18 PM
> To: Maven Users List
> Subject: Re: plugin dependencies question
>
> That's new in 2.0.9. Well, not new, but now it works. ;-)
>
> Wayne
>
> On 3/12/08, Brian E. Fox <br...@reply.infinity.nu> wrote:
> > Yes. Compile against foobar normally. The users can specify the
> > dependency they want in the plugin configuration block. This is
> working
> > in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
> > http://jira.codehaus.org/browse/MNG-2972 for more information.
> >
> > In this way you can say your plugin will use FooBar version x.y by
> > default, but if they want to use another one, they can do so by
> > overriding it in their pom.
> >
> > -----Original Message-----
> > From: Eric Miles [mailto:eric.miles@kronos.com]
> > Sent: Wednesday, March 12, 2008 4:24 PM
> > To: users@maven.apache.org
> > Subject: plugin dependencies question
> >
> > All,
> >
> > I have a plugin I wrote, that use framework FooBar. This plugin will
> > work with FooBar version 1.1 through 1.8. I have numerous maven
> > projects that use my plugin and all use different versions of FooBar.
> > The version of FooBar is important to each project as compilation is
> > performed (compiled units are not backwards compatible). Is there a
> way
> > to create my plugin so that it uses FooBar for compilation, however
> the
> > individual projects specify which version of FooBar to the plugin via
> > the pom?
> >
> > Thanks in advance,
> > Eric Miles
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin dependencies question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Handy, isn't it?
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Wednesday, March 12, 2008 7:18 PM
To: Maven Users List
Subject: Re: plugin dependencies question
That's new in 2.0.9. Well, not new, but now it works. ;-)
Wayne
On 3/12/08, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Yes. Compile against foobar normally. The users can specify the
> dependency they want in the plugin configuration block. This is
working
> in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
> http://jira.codehaus.org/browse/MNG-2972 for more information.
>
> In this way you can say your plugin will use FooBar version x.y by
> default, but if they want to use another one, they can do so by
> overriding it in their pom.
>
> -----Original Message-----
> From: Eric Miles [mailto:eric.miles@kronos.com]
> Sent: Wednesday, March 12, 2008 4:24 PM
> To: users@maven.apache.org
> Subject: plugin dependencies question
>
> All,
>
> I have a plugin I wrote, that use framework FooBar. This plugin will
> work with FooBar version 1.1 through 1.8. I have numerous maven
> projects that use my plugin and all use different versions of FooBar.
> The version of FooBar is important to each project as compilation is
> performed (compiled units are not backwards compatible). Is there a
way
> to create my plugin so that it uses FooBar for compilation, however
the
> individual projects specify which version of FooBar to the plugin via
> the pom?
>
> Thanks in advance,
> Eric Miles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: plugin dependencies question
Posted by Wayne Fay <wa...@gmail.com>.
That's new in 2.0.9. Well, not new, but now it works. ;-)
Wayne
On 3/12/08, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Yes. Compile against foobar normally. The users can specify the
> dependency they want in the plugin configuration block. This is working
> in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
> http://jira.codehaus.org/browse/MNG-2972 for more information.
>
> In this way you can say your plugin will use FooBar version x.y by
> default, but if they want to use another one, they can do so by
> overriding it in their pom.
>
> -----Original Message-----
> From: Eric Miles [mailto:eric.miles@kronos.com]
> Sent: Wednesday, March 12, 2008 4:24 PM
> To: users@maven.apache.org
> Subject: plugin dependencies question
>
> All,
>
> I have a plugin I wrote, that use framework FooBar. This plugin will
> work with FooBar version 1.1 through 1.8. I have numerous maven
> projects that use my plugin and all use different versions of FooBar.
> The version of FooBar is important to each project as compilation is
> performed (compiled units are not backwards compatible). Is there a way
> to create my plugin so that it uses FooBar for compilation, however the
> individual projects specify which version of FooBar to the plugin via
> the pom?
>
> Thanks in advance,
> Eric Miles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: plugin dependencies question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Yes. Compile against foobar normally. The users can specify the
dependency they want in the plugin configuration block. This is working
in 2.0.9, you can see http://jira.codehaus.org/browse/MNG-3426 and
http://jira.codehaus.org/browse/MNG-2972 for more information.
In this way you can say your plugin will use FooBar version x.y by
default, but if they want to use another one, they can do so by
overriding it in their pom.
-----Original Message-----
From: Eric Miles [mailto:eric.miles@kronos.com]
Sent: Wednesday, March 12, 2008 4:24 PM
To: users@maven.apache.org
Subject: plugin dependencies question
All,
I have a plugin I wrote, that use framework FooBar. This plugin will
work with FooBar version 1.1 through 1.8. I have numerous maven
projects that use my plugin and all use different versions of FooBar.
The version of FooBar is important to each project as compilation is
performed (compiled units are not backwards compatible). Is there a way
to create my plugin so that it uses FooBar for compilation, however the
individual projects specify which version of FooBar to the plugin via
the pom?
Thanks in advance,
Eric Miles
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org