You don't need to change dependency plugin itself, but how m2e deals with it inside workspace. But you most likely correct with regards to the time, this will likely be a major effort.
-- Regards, Igor On 12-03-07 2:10 PM, Laird Nelson wrote:
On Wed, Mar 7, 2012 at 1:55 PM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: In short, most likely you need to reimplement all relevant dependency plugin logic to use m2e workspace resolution api. Oh, OK, that's simply not an option at all (not going to couple our build to an integration tool), and I don't have the time to become a committer and "fix" the maven-dependency-plugin which works perfectly fine in all other respects. I guess I'm forced therefore to turn off workspace artifact resolution. I'll see if I can make that fly. Thanks, Laird -- http://about.me/lairdnelson _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
