Eclipse/STS from the Spring guys (VMWare now) is an Eclipse IDE with all
of the plug-ins that you need to develop Java (and more).
We started with pure Eclipse but spent so much time fixing up the
plug-ins with each new version that it affected our productivity.
Once we found the Spring Tool Suite (Eclipse with all the "right"
plug-ins) we were in good shape - 1 download and we were back up and
coding in a few minutes.
I have never used NetBeans so I have no comment about how it helps with
the original problem(source code location).
Ron
On 24/10/2013 6:49 PM, Mark Eggers wrote:
I'm not much of an Eclipse user, but if I remember correctly Kepler
comes with Maven out of the box.
Your mileage may vary (I mostly use NetBeans).
Mark
/mde/
On 10/24/2013 3:37 PM, Robert Dailey wrote:
I do happen to use Eclipse, and all I've installed is the m2e plugin
from Help menu. Is this what you are talking about?
On Thu, Oct 24, 2013 at 3:48 PM, Ron Wheeler
<[email protected]> wrote:
The easy way to figure out what is happening is to use Eclipse/STS
as your
IDE and then you have nice gui tools that will tell you where your
sources
are supposed to be.
It is free and comes ready to build with maven.
It has a nice editor for pom files and a window that shows you what you
effective POM is and another that shows you your whole maven
dependency tree
with nice little notes about version conflicts and which one Maven has
selected for your pleasure.
Ron
On 24/10/2013 4:23 PM, Laird Nelson wrote:
mvn help:effective-pom will spit out the pom made up of the
defaults plus
anything you've overridden or added. Stand back; it's huge.
Best,
Laird
On Thu, Oct 24, 2013 at 1:21 PM, <[email protected]> wrote:
Maven has a 'convention over configuration' philosophy, which
means that
the pom.xml doesn't need to specify paths that are in the
conventional
places. So unless otherwise configured, it will look in
src/main/java
for
all of it's (non-test) source code. You should be able to find the
conventions listed on the maven site, or the site for a particular
plug-in.
I find this very helpful in creating minimalist pom.xml files for the
standard 'make me a jar, test, document, and put it some where it
can be
found' process. But it can be a pain if you don't know where the
conventional places are, and any deviation often results in a great
multitude of google searches to find the man behind the curtain.
--------- Original Message --------- Subject: Trying to understand
how
maven finds source
From: "Robert Dailey" <[email protected]>
Date: 10/24/13 1:04 pm
To: "Maven" <[email protected]>
Hey everyone,
I'm trying to understand something basic, I haven't been able
to find
the answer through Google surprisingly (maybe my searching
abilities
suck today). How is it that Maven is able to find source code to
compile? What I would expect is the pom.xml to refer to some
*.java
path (something like <source>src/main/java/*</source>), but I
don't
see anything like that.
How does maven know what java source code to compile? Thanks in
advance for any help.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
