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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
