Re: [m2e-users] m2e-users Digest, Vol 61, Issue 8

[Thorbjørn Ravn Andersen <thunderaxiom@xxxxxxxxxxx>]

My personal experience is that workspaces are not guaranteed to be re-usable
between different Eclipse instances.

After fully mavenizing our sources and finding that Eclipse does not cope
well with git branches if the maven projects change drastically when
switching branches I have made it a habit to simply create a new workspace
for each task.

By registering a right click action on folders saying "Open as workspace
with Eclipse" it is reasonably easy to work with.


-----Original Message-----
From: m2e-users-bounces@xxxxxxxxxxx [mailto:m2e-users-bounces@xxxxxxxxxxx]
On Behalf Of V. Mark Lehky
Sent: 12. februar 2014 17:57
To: m2e-users@xxxxxxxxxxx
Subject: Re: [m2e-users] m2e-users Digest, Vol 61, Issue 8

I had turned on the digest mode for the mailing list and there is no way
(that I can find) to reply to individual messages?!?! :( I bet this is going
screw up threading. Sorry.

In the end I figured out what the problem is.
I had a file
~/workspace/.metadata/.plugins/org.eclipse.m2e.core/lifecycle-mapping-metada
ta.xml
when deleted the problem went away. Don't know where this file came from,
although I did initially create my workspace in Eclipse-Juno, and did not
change anything when I upgraded to Eclipse-Kepler.

ML

On 12 February 2014 00:58,  <m2e-users-request@xxxxxxxxxxx> wrote:
> Message: 1
> Date: Tue, 11 Feb 2014 10:59:06 -0800
> From: "V. Mark Lehky" <mark.lehky@xxxxxxxxx>
> To: m2e-users@xxxxxxxxxxx
> Subject: [m2e-users] How to add "Maven Managed Dependencies"?
> Message-ID:
>         
> <CAP_tRR8oMKA5N-fUuvkFb4ktuWpTNm46oJ8Gdx4mO+NaQtD0Mw@xxxxxxxxxxxxxx>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello.
>
> I am facing the exact same problem as described here:
>
<https://stackoverflow.com/questions/4859825/how-to-add-maven-managed-depend
encies-library-in-build-path-eclipse>.
> However, none of the posted solutions seem to work for me. Been 
> Googling all day, but still no go. Maybe something changed in the 
> latest Eclipse?
>
> I have "Eclipse IDE for Java Developers", Kepler, Build id:
> 20130919-0819. This comes with M2E version 1.4.0. I only installed the 
> latest updates.
>
> 1. Create a new Maven Project.
> 2. Use "maven-archetype-quick". BTW: I get the same problem if I skip 
> archetype selection.
> 3. Right-click on the project, Properties > Project Facets > Convert 
> to faceted form > add _only_ Java.
> 4. It builds with errors, complaining that JUnit is missing (the 
> archetype above created a AppTest.java). Check the pom.xml, the 
> dependency is there!
> 5. Right-click on the project, Build Path > Add Libraries > Maven 
> Managed Dependencies > Next 6. At this point I am presented with "Use 
> Maven Project settings to configure Maven dependency resolution". Not 
> sure what that is? But I am able to click Finish.
> 7. When I click Finish, nothing happens. I do know for sure that I 
> have JUnit in my local M2/repository already.
> 8. Right-click on the project, Maven > Update Project also does nothing.
>
> As per the link above, I can run `mvn eclipse:eclipse` from the 
> command line to fix the dependencies in Eclipse, but I have to do this 
> for every single added dependency? This does not seem correct? Also, 
> some people in that discussion suggested that this may in fact cause 
> some other problems, but they did not say what.
>
> I have another project in my Eclipse, that has the "Maven 
> Dependencies" library as part of the build path. So the "feature"
> works. Any dependency I add to the pom in _that_ project is 
> automagically added to the Eclipse build path under Maven 
> Dependencies. Unfortunately somebody gave me this already packaged up.
>
> How do I correctly set this up in Eclipse from scratch? What is the 
> obvious thing that I am missing?
>
> TIA for any advice. ML.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users