[m2e-users] Selective

Is it possible to configure a for a plugin that applies to only certain occurrences of the plugin and/or only one of its executions (e.g., based on its )? The problem I'm running into is that I have a Maven project that uses the maven-compiler-plugin for both Java and Groovy compilation, but the

Re: [m2e-users] Selective

t; [2] http://git.eclipse.org/c/m2e/**m2e-core.git/tree/org.eclipse.** > m2e.core/mdo/lifecycle-**mapping-metadata-model.xml<http://git.eclipse.org/c/m2e/m2e-core.git/tree/org.eclipse.m2e.core/mdo/lifecycle-mapping-metadata-model.xml> > > -- > Regards, > Igor > > &g

[m2e-users] Understanding the Maven Project Builder

I'm attempting to convert a large and complex multi-module project environment from m2eclipse (v0.12) to m2e (v1.1). I have things pretty much working well but things are getting messed up by what I assume are differences between the way the Maven Project Builder works in v0.12 vs. v1.1. In parti

Re: [m2e-users] Understanding the Maven Project Builder

itty of it. > > [1] > http://wiki.eclipse.org/M2E_**plugin_execution_not_covered<http://wiki.eclipse.org/M2E_plugin_execution_not_covered> > > -- > Regards, > Igor > > > On 12-08-15 5:47 PM, Nathaniel Mishkin wrote: > >> I'm attempting to convert a large and

Re: [m2e-users] Understanding the Maven Project Builder

couple of bugs in m2e bugzilla that talk about Maven console > oddities, but nobody cared enough to provide a patch > > -- > Regards, > Igor > > > > > On 12-08-15 10:56 PM, Nathaniel Mishkin wrote: > >> Ah, yes, I've looked at that wiki page many times, b

[m2e-users] Problem loading connectors (m2e 1.2)

I'm trying out the latest m2e 1.2 build and I'm running into a problem during import. During the process I get the step to setup Maven plugin connectors. There are several "Install ..." actions listed. I click "Finish" to that step and then the "Install" wizard comes up. I click "Next" but noth

Re: [m2e-users] Problem loading connectors (m2e 1.2)

ry.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-buildhelper/0.15.0/N/0.15.0.201207090124/ > > > HIH > > Fred Bricon > > On Wed, Aug 29, 2012 at 2:01 PM, Nathaniel Mishkin > wrote: > >> I'm trying out the latest m2e 1.2 build and I'm running int

Re: [m2e-users] m2e 1.2 is released

Is there a timeline or a process by which these and other m2e connectors will be published to eclipse.org? On Wed, Sep 19, 2012 at 2:29 PM, Igor Fedorenko wrote: > The version of build-helper-maven-plugin is incompatible with m2e 1.2, > or so it says > > > Cannot satisfy dependency: > From

Re: [m2e-users] m2e 1.2 is released

se > legal process does not allow this. You can publish them to eclipse > marketplace, however. > > -- > Regards, > Igor > > > On 12-09-19 3:13 PM, Nathaniel Mishkin wrote: > >> Is there a timeline or a process by which these and other m2e connectors >> wil

Re: [m2e-users] new m2e catalog published on port 8081

I just tried to import some projects into a fresh Eclipse into which I had just installed m2e 1.2 and it appears to continue to want to go to http://repository.tesla.io:8081/nexus/, which due to corporate firewall stuff is not reachable: Problems occurred while performing installation: Error(s) oc

Re: [m2e-users] new m2e catalog published on port 8081

gt; urls pointing back to the Tesla Nexus instance on port 8081. I still need >> to purge the EdgeCast cache but the right content is up there now. While >> building the catalog the process makes sure that the source repository is >> reachable so if the right connectors.xml file ma

Re: [m2e-users] new m2e catalog published on port 8081

er suggestion... Nat On Tue, Oct 9, 2012 at 2:42 PM, Igor Fedorenko wrote: > Can you try clean/fresh m2e installation? > > -- > Regards, > Igor > > > On 12-10-09 1:31 PM, Nathaniel Mishkin wrote: > >> Unfortunately, I'm still seeing a (faili

[m2e-users] "org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest)"

I have a m2e-imported project that produces this error in the Eclipse "Problems" view: org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest) that's all. Nothing else. The Eclipse Error log contains: !ENTRY org.eclipse.m2e.logback.appender 4 0 2012-11-30 15:

Re: [m2e-users] "org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest)"

Krzewski > wrote: > >> Nat, >> >> have you checked the "secret" m2e log in >> .metadata/.plugins/org.eclipse.m2e.logback.configuration/0.log? >> >> Cheers, >> Rafał >> >> >> On 11/30/2012 09:34 PM, Nathaniel Mishkin wrote:

[m2e-users] Eclipse launcher classpath and Maven dependencies

Here's my situation: Project A depends on Project B at runtime only. Project A's POM doesn't declare a dependency on Project B. Since Project A will never be launched or packaged in final form from Maven, I think this is reasonable. However, I want to debug Project A (and B) from Eclipse so I c

Re: [m2e-users] Eclipse launcher classpath and Maven dependencies

tell the tooling, > i.e. Maven or m2e, about this runtime dependency so tooling has the > chance to do the right thing for you. > > -- > Regards, > Igor > > > On 2013-02-15 11:54 AM, Nathaniel Mishkin wrote: > >> Here's my situation: >> >> Project

[m2e-users] Mysterious maven-jar-plugin returns

Last year (see http://dev.eclipse.org/mhonarc/lists/m2e-users/msg03633.html) I reported an m2e issue I was having with the maven-jar-plugin, the short story being the error: org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest) The suggested workaround (downgr