Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4FD0ABC1.1070509@artifact-software.com>
Date: Thu, 07 Jun 2012 09:25:21 -0400
From: Ron Wheeler <rwheeler@artifact-software.com>
Reply-To: rwheeler@artifact-software.com
Organization: Artifact Software
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: users@maven.apache.org
Subject: Re: migrating from Eclipse to a Maven build
References: 
 <CAGZ5p6+SmBGu1tKXK2=Gygmmsw7eJEmpLijQFEr1gnpt5ejTHw@mail.gmail.com>
In-Reply-To: 
 <CAGZ5p6+SmBGu1tKXK2=Gygmmsw7eJEmpLijQFEr1gnpt5ejTHw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

My 2 cents.
Move from Eclipse to Eclipse STS from Springsource.
This gives you an Eclipse ready to go out-of-the-box with Maven and 
everything else you need to develop in Java.

I believe that you can then add the maven nature to your project.

Adjust the Maven POM, if required, to point to your source directory as 
it is. Maven is pretty flexible about many things.

Add the dependencies that you need to the POM.

At that point, you should be able to build in Eclipse with Maven. Just 
point at the POM=> right click => Run As and select the Maven goal that 
you want to run.

Not a big deal.

For new projects, just tell STS that you want a maven project and it 
will build you one that works once you add your dependencies.

If you don't want to go to STS you can manually add m2 plug-in and 
whatever else you need.
We started that way (plain Eclipse) but just lost so much time screwing 
around with Eclipse plug-ins on every new Eclipse release that we moved 
to STS. One donwload and a quick install and your new version of Eclipse 
is ready to go.

We never use Maven outside Eclipse but others do.

Ron


On 07/06/2012 8:59 AM, Ronald Albury wrote:
> I have seen much documentation of importing a Maven project into Eclipse.
>   However, many of us have the opposite situation - we are starting with an
> Eclipse set-up and have decided to migrate to Maven for the builds.
>
> I did find one posting on the subject - the author, like myself, was
> intimidated by Maven ... and especially intimidated by the differences in
> the directory layout between Maven and Eclipse.  However, he said that
> since he was well experienced in Eclipse he was able to muddle thru it.
>   Muddle thru it how?  The only thing I can think of is to start by building
> a Maven set-up, manually moving my Eclipse files into the Maven projects,
> and then importing back into Eclipse.
>
> Surely there is a better way than that!
>
> Thanks for your patience and your assistance,
>     RonA
>


-- 
Ron Wheeler President Artifact Software Inc email: 
rwheeler@artifact-software.com skype: ronaldmwheeler phone: 
866-970-2435, ext 102

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org