Hi,
I have installed Eclipse Indigo for the first time today and enjoyed
installing M2E from the standard update site. Opening a complex Maven
project, I notice that most of my POM's display an error message like
the following:
Plugin execution not covered by lifecycle configuration:
org.apac
Ben, you sound like you could at least explain what's going on? So
far, I found no explanation at all?
On Thu, May 26, 2011 at 8:49 PM, Ben Tatham wrote:
> Can someone please explain to me why we have to add all
> the pluginExecutionFilters for all of the specific plugins eveywhere to work
> aro
Thanks, Igor, for the explanation. Let me summarize, what I read from that:
Because of some "long-standing issues" and some "rogue maven plugins"
you choosed to invent a system that enforces registration of every
Maven plugin in the so-called lifecycle configuration.
Rather than assuming a meanin
On Fri, May 27, 2011 at 6:02 AM, Igor Fedorenko wrote:
> Of course, there is a chance we overlooked another, simpler solution, so
> if you think you know how to make m2e work reliably and efficiently with
> all/many projects while failing gracefully for the rest, please bring
> this up on m2e-dev
On Fri, May 27, 2011 at 3:45 PM, Igor Fedorenko wrote:
> I wish it was that simple.
Igor, you know much more about the plugin than I do. But you can't
convince me that doing things this way was an unlucky decision.
Indeed, I can very easily proof my theory: Without that decision, you
wouldn't ne
On Sat, Jun 25, 2011 at 11:06 AM, Igor Fedorenko wrote:
> To be clear, adding mapping to pom.xml is almost certainly
> not a good idea, especially for maven plugins that generate code in
> eclipse workspace. Wiki [1] provides some background information about
> bad side-effects of executing mave
>
> On 11-06-25 3:38 PM, Jochen Wiedmann wrote:
>>
>> On Sat, Jun 25, 2011 at 11:06 AM, Igor Fedorenko
>> wrote:
>>
>>> To be clear, adding mapping to pom.xml is almost certainly
>>> not a good idea, especially for maven plugins that generat
On Mon, Jun 27, 2011 at 11:16 AM, Moser, Christian wrote:
> Thank you for the interesting discussion. Regarding your feedback, I still
> think a change is necessary and filled a bug, please vote.
>
>
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
Christian, just as a hint: Voting does
On Mon, Jun 27, 2011 at 3:07 PM, Igor Fedorenko wrote:
> For example, none of "mojo" enhancement
> requests we received so far [1] can be supported by neither
> nor mapping, so improving ways to stores these mappings seems
> like a wrong problem to solve.
After reading that list, I am really u
On Thu, Jun 30, 2011 at 5:55 PM, Igor Fedorenko wrote:
> I am not following. Why does version=1.0.0 forbid specifying lifecycle
> mapping in parent pom?
Dunno, but the NPE is most likely related to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=347602
--
Capitalism is the astounding belief
Hi,
just like to point your attention to
http://grumpyapache.blogspot.com/2011/08/mess-that-is-m2e-connectors.html
It should be better to read there, but I am quoting for the sake of
discussion below:
The mess that is m2e connectors
Warning: The following is most likely stubborn,
unreason
rds,
> Igor
>
> On 11-08-27 8:52 PM, Jochen Wiedmann wrote:
>>
>> Hi,
>>
>> just like to point your attention to
>>
>> http://grumpyapache.blogspot.com/2011/08/mess-that-is-m2e-connectors.html
>>
>> It should be better to read there, bu
Just as a note: Sounds like a useful thing to have, but only with an
additional preference option "read/only index".
On Wed, Apr 25, 2012 at 2:27 PM, Cèsar Ordiñana wrote:
> Hi.
>
> I'm working with many related projects, having each one on its own eclipse
> workspace. On each of those workspaces
I too am getting more and more frustrated with M2Eclipse. A missing
"Maven Dependencies" library is just the usual case lately and there
is no easy way to get it back, apart from "Update Project", which
rarely works as expected and never leaves a useful error message.
Jochen
On Wed, Jul 25, 201
On Wed, Jul 25, 2012 at 1:28 PM, Igor Fedorenko wrote:
> Open bug reports, provide small standalone examples that demontsrate the
> problem, ideally provide patches that fix the problems. We really can't
> help unless you tell us about the problems and work with us on the fix.
You're certainly ri
On Thu, Jul 26, 2012 at 9:03 AM, SoftwareEngineering Hauschel
wrote:
> hi,
> i'm using juno with the m2e plugin, if i checkout a project as maven project
> from svn or import one from filesystem "Import Existing Maven Project" so my
> src folders are not always identified.
> close/open Project, Re
On Thu, Aug 16, 2012 at 4:31 AM, Zhang, Xueqian wrote:
> Basically we wonder if there's a way to suppress the 'M2E plugin execution
> not covered' error in pom.xml. For unknown maven plugins to m2e, we want to
> skip them by default without modifying pom.xml. We want to provide a flag so
> tha
On Wed, Feb 20, 2013 at 2:22 PM, SoftwareEngineering Hauschel <
i...@hauschel.de> wrote:
> Hi there,
> no I start with low level actions.
> New Eclipse:
> and m2e:If I "import an existing maven project" from file system, the
> project's src folder is not recognized.
>
> Any Idea ?
>
>
Same problem
On Thu, May 30, 2013 at 10:55 AM, Max Rydahl Andersen <
max.ander...@redhat.com> wrote:
> I completely understand the reasoning for moving, but I hate to be the one
> break the news but users are not by far having adopting Java 7 as their
> preferred
> runtime.
>
I beg to distinguish between my "
Please, guys, keep the following in mind:
- Installing, or updating Eclipse can be done without administrative
privileges.
- Installing, or updating a JRE does.
Not all of us have root permissions, in particular not the Windows users.
Jochen
On Fri, May 31, 2013 at 8:34 AM, Tonny Madsen wrote
I like your first comment in the bug. :-)
On Thu, Jun 5, 2014 at 3:09 AM, Igor Fedorenko wrote:
> I just published new m2e release candidate build. No code changes, but one
> IP-related fix.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=436644
>
> --
> Regards,
> Igor
>
Does this one contain a fix for the maven.multiModuleProjectDirectory?
On Wed, Apr 15, 2015 at 10:02 PM, Fred Bricon wrote:
> Hello World,
>
> m2e 1.5.2 (git tag 'releases/1.5/1.5.2.20150413-2215') has been promoted to
> the release update site [1].
> You can now use Maven 3.3.1 as an external r
Hi, Lars,
have you tried to disable "Download repository updates on startup"?
Jochen
On Thu, Oct 1, 2015 at 12:32 PM, Max Rydahl Andersen
wrote:
> I'm curious - how do you avoid having colliding builds if you share local
> Repo?
>
>
>
> /max
> http://about.me/maxandersen
>
>
>> On 30 Sep 2015
Main question here: As M2E is obviously building the project model
anyways, and internally (for example to maintain, and display the list
of "Maven Dependencies"), is it really necessary to rebuild that?
On Wed, Oct 7, 2015 at 1:28 PM, Andi Scharfstein
wrote:
> Hello,
> we recently introduced m2
Hi,
subject says it all. What I did try:
1.) Import the project as an "existing Maven project" (that worked
fine, of course), followed by Team->Share Project. Selected "Git" as
repository type, and clicked on either "Next", or "Finish". Nothing
happens.
2.) Import the project via "Checkout Maven
Hi, Lars,
didn't really check, but I assume that this configures the Profiles,
which are being activated whenever Maven is building the project. You
can configure, what is most likely the same list via Project
Properties/Maven/"Active Maven Profiles".
Profiles are typically used to adapt a Maven
You aren't using JDK9, are you?
On Wed, Dec 16, 2015 at 10:59 AM, Benjamin Maurer
wrote:
> Hi all,
>
> I’m having issues with M2E and the maven-jaxb2-plugin
> (org.jvnet.jaxb2.maven2:maven-jaxb2-plugin).
>
>
>
> Running the build from the command line works just fine, but in Eclipse I
> get an E
Hi,
whenever I try to install M2E into Eclipse 4.6RC3, I get an error like below
Is there any other possibility to get M2E running?
Thanks,
Jochen
An error occurred while collecting items to be installed
session context was:(profile=SDKProfile,
phase=org.eclipse.equinox.internal.p2.engine.pha
I get the message below:
Operation details
Cannot complete the install because one or more required items could
not be found.
Software being installed: Maven SCM Handler for EGit
0.14.0.201509090157 (org.sonatype.m2e.egit.feature.feature.group
0.14.0.201509090157)
Missing requirement: Maven SCM Ha
29 matches
Mail list logo
