That's new in 2.0.9. Well, not new, but now it works. ;-) Wayne
On 3/12/08, Brian E. Fox <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED] > Sent: Wednesday, March 12, 2008 4:24 PM > To: [email protected] > 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: [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]
