maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Dailey <>
Subject Re: Trying to understand how maven finds source
Date Thu, 24 Oct 2013 20:33:30 GMT
I tried your command and I got this:

C:\Work\maven>mvn help:effective-pom
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 0.414s
[INFO] Finished at: Thu Oct 24 15:32:04 CDT 2013
[INFO] Final Memory: 12M/306M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
(default-cli): Goal requires a project to execute but ther
e is no POM in this directory (C:\Work\maven). Please verify you
invoked Maven from the correct directory. -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]

There is no pom.xml in this directory. Should it be trying to build a
package if I am specifying "help"?

On Thu, Oct 24, 2013 at 3: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, <> 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" <>
>> Date: 10/24/13 1:04 pm
>> To: "Maven" <>
>> 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:
>>  For additional commands, e-mail:
> --

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message