I use Eclipse and the External Tools configuration to run mvn from
within eclipse if needed.
I used to have Eclipse compiling to a different classes directory and
that worked fine for many projects, but recently I use 'mvn
jetty:run' all the time so that when I save a java file in Eclipse it
I don't currently use any of the Maven Eclipse IDE integration plugins
and just use
Eclipse's external tools facility to run mvn for any selected folder
in Eclipse's 'Package Explorer' pane.
At least this way you know Maven is behaving as it does from the
command line, for new dependency I add to
Since we're talking about Eclipse... As I said before, I'm using SAP
NWDS (2.0.14) which is based on Eclipse v2.1. I'm using
eclipse:eclipse to generate metadata and added the proper perspectives
etc.
When I create a new project (J2EE, EJB Module Project or Web Module
Project) then it shows up in
Thierry is definitely right that you can run into inconsistencies between
the incremental Eclipse builds versus Maven builds. I've had to do
occasionally some Project-Cleans to get rid of the red.
Wayne I would DEFINITELY upgrade to an Eclipse 3.x product. I think in
general you would be better
I'd take a look at what files are generated when you create a new project
using SAP. Are there other folders / files that are created? (starting
with a dot).
Are there project natures / builders that are not being included (in the
.project file)?
It sounds like there is *something* missing
There can be problems caused with a single build destination caused by the
Eclipse incremental compiler that would sometimes require doing a clean in
both maven and eclipse.
On 9/14/07, Jim Sellers [EMAIL PROTECTED] wrote:
I've used separate locations for a few reasons:
1) in web apps to keep
You must this dependency to the pom add.
zm schrieb:
Hi,
Can anyone help me with the best way to setup a Maven/Eclipse environment? I
know there is a goal to produce an eclipse project with the pom, but I'm
trying to understand how to create one at hand, customise and include it's
$ mvn eclipse:m2clipse
seems to works really well for me in Eclipse3.3. It creates a
M2Libraries that automatically loads the jars into eclipse classpath.
The only trouble I have is if I want my project to have WTP nature
enable... I've used
$ mvn eclipse:m2clipse -Dwtpversion=1.5
but then I have
That's interesting - why separate locations? To avoid having to refresh in
Eclipse when a maven build is run?
On 9/13/07, Jim Sellers [EMAIL PROTECTED] wrote:
I've had the most success with using maven and eclipse by:
1) having both systems build to a separate locations
2) using command line
Since you brought that up, let me take advantage of this oportunity to ask
users:
I have always used m2. How would that compare to q4e?
Thanks,
Rodrigo
On 9/14/07, Dave Feltenberger [EMAIL PROTECTED] wrote:
That's interesting - why separate locations? To avoid having to refresh
in
Eclipse
I haven't had the time/inclination to try out q4e yet. I didn't like m2
when I tried it a few weeks ago, though. I'd be interested to see what
people think of q4e so far...
On 9/14/07, Rodrigo Madera [EMAIL PROTECTED] wrote:
Since you brought that up, let me take advantage of this oportunity
I've used separate locations for a few reasons:
1) in web apps to keep the default location (WEB-INF/classes)
2) in eclipse it'll build to one location, in maven it builds to 2 (classes,
test-classes) and I wanted to keep that behaviour
3) if I run mvn clean or mvn site (etc), I don't have to do a
I'll have to give this a try. I agree having Eclipse do a rebuild is
painful sometimes, especially if there are a lot of projects. I never
really thought about having two separate output directories, for some
reason.
One more experiment to add to the to-do list...
On 9/14/07, Jim Sellers
Maven and Eclipse are tricky to get together well.
I use m2, and from time to time I've lost hours of otherwise productive time
trying to figure out why things were not working. I could name a lot of
issues, like dependency problems and removed compiled classes that weren't
being rebuilt.
-Original Message-
From: Jim Sellers [mailto:[EMAIL PROTECTED]
Sent: Friday, September 14, 2007 3:23 PM
To: Maven Users List
Subject: Re: Eclipse and Maven best practice
I've used separate locations for a few reasons:
1) in web apps to keep the default location (WEB-INF/classes
Wow... sorry for so many typos. I'm in a serious rush.
Here's my previous email with applied corrections:
Maven and Eclipse are tricky to get together well.
I use m2, and from time to time I've lost hours of otherwise productive
time trying to figure out why things were not working. I could
http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html
http://m2eclipse.codehaus.org/
http://code.google.com/p/q4e/
-Original Message-
From: zm [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 13, 2007 10:54 AM
To: users@maven.apache.org
Subject: Eclipse and Maven best
Is there any reason why you don't use a Maven/Eclipse plugin such as
m2eclipse and now q4e? They integrate fully into Eclipse's build and do
autodependency management. Also have you setup a CLASSPATH Container
variable within Eclipse in order to use your local M2 repository?
See here:
Hi,
It give a book a Better Builds with Maven vor free on the page:
http://www.devzuz.com/web/guest/products/resources#BBWM. I think it help
you.
Alexander Vaysberg (pc-hilfe)
zm schrieb:
Hi,
Can anyone help me with the best way to setup a Maven/Eclipse environment? I
know there is a goal to
I'm recently involved in an SAP NWDS (NetWeaver Dev Studio) project at
work. NWDS is really just Eclipse 2.1 with some SAP-specific stuff
added.
Among the things they took away in this customized Eclipse is the
ability to add plugins etc the usual way through the menu system.
I'm wondering if
I've had the most success with using maven and eclipse by:
1) having both systems build to a separate locations
2) using command line to run maven and when I need to sync up metadata using
eclipse:eclipse then hitting refresh in eclipse.
3) for any eclipse specific data (.classpath, .mymetadata,
This is the way I generally work, too. I just thought maybe I'd look
into one of these new tools since I'm back in Eclipse regularly and
have never really given any of these tools a chance.
Wayne
On 9/13/07, Jim Sellers [EMAIL PROTECTED] wrote:
I've had the most success with using maven and
Wayne,
I don't think you are going to get an m2e for Eclipse 2 and q4e, as I
remember, is for 3.3 (but maybe it works with 3.2 too).
But you can install pretty much as many versions of Eclipse as you want each
working on a different part of your code. Just put them in different
folders. I even
23 matches
Mail list logo
