maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Dailey <rcdailey.li...@gmail.com>
Subject Re: Trying to understand how maven finds source
Date Thu, 24 Oct 2013 22:37:13 GMT
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
<rwheeler@artifact-software.com> 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, <randysr@kamradtfamily.net> 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" <rcdailey.lists@gmail.com>
>>> Date: 10/24/13 1:04 pm
>>> To: "Maven" <users@maven.apache.org>
>>>
>>> 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: users-unsubscribe@maven.apache.org
>>>   For additional commands, e-mail: users-help@maven.apache.org
>>>
>>
>>
>
>
> --
> 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
>

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


Mime
View raw message