Just FYI, last week, I've added https://github.com/ianbrandt/m2e-maven-dependency-plugin#m2e-connector-for-the-maven-dependency-plugin to m2e's discovery catalog.
So if you want to contribute, well, this is github. Fred On Wed, Oct 1, 2014 at 8:19 AM, Igor Fedorenko <[email protected]> wrote: > There is no reactor during m2e workspace build, each project is built > independently. > > Normally, projects resolve dependencies from workspace before checking > local/remote repositories. Workspace dependency resolution can be > disabled, but this most likely isn't what you want. > > It is possible change dependency plugin to copy with unpacked > dependencies, as I suggested in MDEP-187. It is also possible to > reimplement relevant dependency-plugin functionality in your connector. > This is probably the easiest short-term solution. Or you can implement > new maven plugin that does what you need and works with unpacked > dependencies. > > Other notes and observations > > If configurator simply delegates to the mojo, it is almost always better > to enable m2e integration in the maven plugin itself, as explained in > [1]. This way your users will not need to install any additional eclipse > plugins, everything will "just work". > > You need to decide what happens during eclipse workspace incremental > build. Your configurator (or the plugin) will be called each time > anything project resource is changed, so you need to make absolutely > sure your configurator does not change filesystem on each execution. > > Also, please use m2e-dev to ask any follow-up questions you might (and > this kind of questions in general). > > [1] https://wiki.eclipse.org/M2E_compatible_maven_plugins > > -- > Regards, > Igor > > > On 2014-10-01, 8:02, CoderPlus Team wrote: > >> Hi all, >> I'm trying to create a connector for the maven-dependency-plugin (copy, >> unpack goals etc). If the dependency which has to be copied or unpacked >> is already open in the workspace, while executing the mojo via a >> configurator, then the plugin throws the below error >> >> /Artifact has not been packaged yet. When used on reactor artifact, copy >> should be executed after packaging: see MDEP-187 is thrown/ >> >> >> This doesn't go away if the dependent project is configured to package >> the dependency during an m2e build. >> >> >> So,basically I'm trying to detach the dependent project from the reactor >> before invoking the plugin via m2eclipse and add it back after the >> execution. >> >> Is this possible? Is it possible to programatically find out what all >> artifactitems are part of the build reactor and remove the ones you want >> to exclude? >> >> >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> _______________________________________________ > m2e-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/m2e-dev > -- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
