But you were not talking about an adapter solution, were you? /Anders (mobile) Den 6 aug 2012 16.28 skrev "Jesse Glick" <jgl...@cloudbees.com>:
> On 08/03/2012 09:15 AM, Anders Hammar wrote: > >> What's the benefit of this approach rather than just having the user >> adding the dependencies directly to the plugin (execution) declaration? >> > > Linkage safety. If you have the-plugin built directly against > the-build-tool@1.1.2, and the user configures it to run against > the-build-tool@1.0-beta-3 or @1.6.3 etc., it > is hard to say in advance what will happen - it might work fine, or it > might consistently throw errors due to signature changes in the-build-tool, > or it might work in > most cases but throw errors in unusual circumstances when certain code > paths are executed. Using an adapter allows the-plugin author to explicitly > manage different > versions of the-build-tool. If the-build-tool has a very simple and stable > interface it would be overkill. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org> > For additional commands, e-mail: dev-h...@maven.apache.org > >
