Good day,
Personally, I still use maven in the command line, and Eclipse as an editor.
What I do is that
1. I go to the directory of my maven project
2. Do mvn eclipse:clean eclipse:eclipse ( eclipse:clean is to make sure
I start with a clean slate )
3. Then create the eclipse project from an
My biggest point of confusion on this is the intermingling of the Build
Path set within Eclipse (which creates a .classpath file) and the
dependencies set in the pom.xml. How are these the same, and how are the
different? Do both still need to be used?
So in your case are you not using any Maven
I'm using this in my pom.xml :
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
This
For Maven to work, you need the dependencies set up properly in your
pom.xml file.
For Eclipse to work, you need the build path set up properly in your
.classpath file.
The Maven Eclipse plugin simply writes out an Eclipse .classpath file
from the dependencies listed in your Maven pom.xml, so
Oh wow, that sounds handy.
Now is there an Eclipse plugin you could recommend that does that all from
within Eclipse? Currently I do nearly all development within Eclipse, and
I'd strongly prefer not to have to jump back and forth from command-line
outside Eclipse to a GUI within it...I prefer
Good day,
As for the first question, please refer to Wayne's answer.
As for the second one, - Yes. I edit the pom.xml file just like a regular
xml file. For more info, kindly see [1].
And as for the third one, please refer to nico's answer.
Cheers,
Franz
[1]
I don't use Eclipse much of the time so I'm probably not the right
person to ask. I switch between Eclipse, Netbeans, Idea, and other
tools depending on what I'm doing.
Rather than rely on IDE plugins, I just use Maven from the command
line. I'd suggest you just plan to get used to the command
What I do which I find very helpful is the following:
project name=MyProject default=package
property environment=env/
property file=build.properties/
property name=project.dir location=./
property name=mvn value=${env.MAVEN_HOME}\bin\mvn.bat/
!-- Feel free to remove the
This Eclipse plugin does a decent job of consolidating M2 and Eclipse...
http://maven.apache.org/eclipse-plugin.html
It creates an Eclipse classpath container that is dynamically loaded from
the pom.xml (or from the parent and child pom.xml files if there are
embedded child modules).
On
Yea I use it as well for exactly that (classpath container variable). Works
great!
-aps
On 2/14/07, Thierry Lach [EMAIL PROTECTED] wrote:
This Eclipse plugin does a decent job of consolidating M2 and Eclipse...
http://maven.apache.org/eclipse-plugin.html
It creates an Eclipse classpath
It creates an Eclipse classpath container that is dynamically loaded from
the pom.xml (or from the parent and child pom.xml files if there are
embedded child modules).
I'm not sure what is meant by the above line (beginner :) Could you please
expand, as it sounds interesting and relevant to
Eclipse defines certain dependencies in its plugin framework as classpath
containers variables (see Eclipse doc). Basically what the Eclipse plugin
does (and you can verify by looking at your .classpath file of your project)
is create a dynamic classpath container that is connected to your
PROTECTED] Im Auftrag von
franz see
Gesendet: Mittwoch, 14. Februar 2007 12:02
An: users@maven.apache.org
Betreff: Re: [m2] Maven from command-line only?
Good day,
Personally, I still use maven in the command line, and Eclipse as an editor.
What I do is that
1. I go to the directory of my
13 matches
Mail list logo
