Thanks Gruss for the details, I tried mvn -U help:effective-pom -Doutput=epom.xml, and find sourceDirectory is without "main" directory in the middle, which conform to what compiles actually when I execute mvn package.
Then I tried mvn -U org.apache.maven.plugins:maven-dependency-plugin:2.10:display-ancestors, here are the output, looks no super POM for me? Any further thoughts are appreciated. I am using IntelliJ 14 Community edition, not sure if any thing did by IntelliJ to change sourceDirectory? Thanks. [INFO] No Ancestor POMs! [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 14.085 s [INFO] Finished at: 2015-04-16T15:36:57-08:00 [INFO] Final Memory: 13M/245M [INFO] ------------------------------------------------------------------------ regards, Lin On Wed, Apr 15, 2015 at 3:25 PM, Bernd Eckenfels <e...@zusammenkunft.net> wrote: > Am Wed, 15 Apr 2015 14:49:21 -0700 > schrieb Lin Ma <lin...@gmail.com>: > > > The document is very helpful. Any thoughts how to check why > > src/java/com/foo/goo works is great. Is there some other files like > > super POM or other files to check? Thanks. > > You can print out the effective pom and check if sourceDirectory is > set or if the compiler plugin has a modified configuration: > > mvn -U help:effective-pom -Doutput=epom.xml > > The completely resolved pom is in epom.xml. If you want to know what > parent poms (up to the root) have been visited, you can use: > > mvn -U > org.apache.maven.plugins:maven-dependency-plugin:2.10:display-ancestors > > Gruss > Bernd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
