I've been using maven for a quiet long time now, and I'm still at a loss
when trying to understand the philosophy behind M2E.
In my view, Maven config defines the project, the IDE reads it, and that's
it.
Not the other way around: having errors like "M2E plugin execution not
covered" just doesn't
On 4 October 2012 11:12, Jean Seurin wrote:
> I've been using maven for a quiet long time now, and I'm still at a loss
> when trying to understand the philosophy behind M2E.
>
> In my view, Maven config defines the project, the IDE reads it, and that's
> it.
>
> Not the other way around: having er
The simple answer, IMHO, is that you want incremental build support.
That's what m2e tries to give you. As Maven and its plugins doesn't
support that, m2e can't delegate it. Forcing a Maven build (even if it
would just be part of the full lifecycle) would give you a very slow
Eclipse environment. T
I'm surprised doing an easy `mvn install` on each every component manually
is not considered 'incremental build' by the community …
:) ok, just joking
thanks for that brief and enlightening comment.
I get it now, and I think M2E is worth a new configuration attempt to get
that legendary 'increme
Hi,
it seems that the new discovery catalog for m2e 1.2 try to contact the
service http://repository.tesla.io:8081/nexus/
Port 8081 it's not very "corporate friendly" because usually network
firewall permits only traffic on port 80 or 443 and for this reason I
cannot install any connector...
Is thi
M2e 1.2 now supports placing your lifecycle mapping metadata in a
global location so that it doesn't need to pollute individual project
poms. This at least addresses one of your original concerns. To do
this, there is now a second quickfix in your pom editor to handle
lifecycle mapping metadata m
Looking at the non test version it appears to not use 8081 for the main
discovery downloads:
http://download.eclipse.org/technology/m2e/discovery/directory-1.1.xml
However, many of the individual components are still hosted at
http://repository.tesla.io:8081/nexus/ which makes those components
di
Is it also fair to say that m2e is the bridge between a Maven project (POM)
and the Eclipse project settings? Since Eclipse doesn't have native
support for Maven, m2e converts the POM to an Eclipse project and then
attempts to keep them synchronized through the build/test/deploy/debug
lifecycle vi
Well, synchronized suggests a two way process. This is not what m2e does,
it cannot update your pom based on changes you make in the project
properties in eclipse.
On Thu, Oct 4, 2012 at 6:09 PM, Jeff wrote:
> Is it also fair to say that m2e is the bridge between a Maven project
> (POM) and the
> M2e 1.2 now supports placing your lifecycle mapping metadata in a global
> location so that it doesn't need to pollute individual project poms.
This doesn't work (1.2 can't be installed) if any of your m2e connectors (i.e.
JiBX) haven't been updated to support 1.2. This makes 1.2 unusable for
> Is it also fair to say that m2e is the bridge between a Maven project (POM)
> and the Eclipse project settings? Since Eclipse doesn't have native support
> for Maven, m2e converts the POM to an Eclipse project and then attempts to
> keep them synchronized through the build/test/deploy/debug l
On 12-10-04 6:23 AM, Tim Pizey wrote:
Or at least make it a Warning not an Error.
I actually joined this list because of this, and found the relevant
code but could not figure out
how to feedback the simple fix.
You need to attach a patch to corresponding bugzilla and convince me and
other m2
I will be giving a talk about difficulties integrating maven and eclipse
at eclipse con eu at the end of the month [1]. Anyone interested to
understand what happens under the hood of m2e and why is welcome to join.
[1]
http://www.eclipsecon.org/europe2012/sessions/m2e-exercise-mixing-oil-and-wat
One thing at a time. I've been focused on getting the infrastructure up. I will
eventually sync the connectors to central and then there won't be any problems.
I have other services running on port 80 internally on that machine so it's not
easy for me to flip it right now. I'll switch it as soon
Excellent! Thanks Jason.
Mike
On Thu, Oct 4, 2012 at 12:57 PM, Jason van Zyl wrote:
> One thing at a time. I've been focused on getting the infrastructure up. I
> will eventually sync the connectors to central and then there won't be any
> problems. I have other services running on port 80 int
15 matches
Mail list logo
