Re: Trying to understand how maven finds source
On Thu, Oct 24, 2013 at 10:34:39PM -0400, Ron Wheeler wrote: 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). NetBeans helps quite a lot. I've been shamefully spoiled by it and tend to use it even just to browse code when I have no intent to develop it. I've used Eclipse (not STS though) and was happy to see the back of it after losing too much time to plugins-disease. I hear that IntelliJ is good with Maven projects too. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature
Re: Trying to understand how maven finds source
Maybe it is mustard after the mail (as the Dutch call it. ;) ), but here is a nice article about the standard directory layout of Maven: http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Hth, Nick Stolwijk ~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~ Lord Baden-Powell On Thu, Oct 24, 2013 at 10:04 PM, Robert Dailey rcdailey.li...@gmail.comwrote: 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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Trying to understand how maven finds source
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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
You are likely not see src/main/java in POMs because that is the default path. Unless you want to change the source directory, you can omit it altogether. On Thu, Oct 24, 2013 at 3:04 PM, Robert Dailey rcdailey.li...@gmail.comwrote: 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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Cheers, Paul
RE: Trying to understand how maven finds source
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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
If you have a look at the effective pom, which is what Maven uses, you will see a sourceDirectory element in the build section. The default path is defined in the Super-POM. You can view the effective pom in m2e or with mvn help:effective-pom. /Anders On Thu, Oct 24, 2013 at 10:08 PM, Paul Benedict pbened...@apache.orgwrote: You are likely not see src/main/java in POMs because that is the default path. Unless you want to change the source directory, you can omit it altogether. On Thu, Oct 24, 2013 at 3:04 PM, Robert Dailey rcdailey.li...@gmail.com wrote: 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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Cheers, Paul
Re: Trying to understand how maven finds source
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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- http://about.me/lairdnelson
Re: Trying to understand how maven finds source
Thanks everyone, super helpful information. I'm still learning so I appreciate you putting up with my silly newbie questions :) I'll try to ramp up on the conventional aspects of maven, that seems to be the missing piece. On Thu, Oct 24, 2013 at 3:24 PM, Anders Hammar and...@hammar.net wrote: If you have a look at the effective pom, which is what Maven uses, you will see a sourceDirectory element in the build section. The default path is defined in the Super-POM. You can view the effective pom in m2e or with mvn help:effective-pom. /Anders On Thu, Oct 24, 2013 at 10:08 PM, Paul Benedict pbened...@apache.orgwrote: You are likely not see src/main/java in POMs because that is the default path. Unless you want to change the source directory, you can omit it altogether. On Thu, Oct 24, 2013 at 3:04 PM, Robert Dailey rcdailey.li...@gmail.com wrote: 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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Cheers, Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
I tried your command and I got this: C:\Work\mavenmvn help:effective-pom [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] BUILD FAILURE [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 org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom (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] [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] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException 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 ljnel...@gmail.com 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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- http://about.me/lairdnelson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
No, but it requires a project (a pom.xml) to be able to calculate an effective pom. /Anders On Thu, Oct 24, 2013 at 10:33 PM, Robert Dailey rcdailey.li...@gmail.comwrote: I tried your command and I got this: C:\Work\mavenmvn help:effective-pom [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] BUILD FAILURE [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 org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom (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] [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] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException 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 ljnel...@gmail.com 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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- http://about.me/lairdnelson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
Oh I understand now, sorry I thought it was a sample POM or something :-) Works when I step into my project directory and run it. Thanks! On Thu, Oct 24, 2013 at 3:37 PM, Anders Hammar and...@hammar.net wrote: No, but it requires a project (a pom.xml) to be able to calculate an effective pom. /Anders On Thu, Oct 24, 2013 at 10:33 PM, Robert Dailey rcdailey.li...@gmail.comwrote: I tried your command and I got this: C:\Work\mavenmvn help:effective-pom [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Stub Project (No POM) 1 [INFO] [INFO] [INFO] BUILD FAILURE [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 org.apache.maven.plugins:maven-help-plugin:2.2:effective-pom (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] [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] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MissingProjectException 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 ljnel...@gmail.com 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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- http://about.me/lairdnelson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Re: Trying to understand how maven finds source
I think I speak for most of us when I say: after mastering maven, we find plenty of other things to be newbies at. So we're all in different instances of the same boat class - Original Message - Subject: Re: Trying to understand how maven finds source From: Robert Dailey rcdailey.li...@gmail.com Date: 10/24/13 1:29 pm To: Maven Users List users@maven.apache.org Thanks everyone, super helpful information. I'm still learning so I appreciate you putting up with my silly newbie questions :) I'll try to ramp up on the conventional aspects of maven, that seems to be the missing piece. On Thu, Oct 24, 2013 at 3:24 PM, Anders Hammar and...@hammar.net wrote: If you have a look at the effective pom, which is what Maven uses, you will see a sourceDirectory element in the build section. The default path is defined in the Super-POM. You can view the effective pom in m2e or with mvn help:effective-pom. /Anders On Thu, Oct 24, 2013 at 10:08 PM, Paul Benedict pbened...@apache.orgwrote: You are likely not see src/main/java in POMs because that is the default path. Unless you want to change the source directory, you can omit it altogether. On Thu, Oct 24, 2013 at 3:04 PM, Robert Dailey rcdailey.li...@gmail.com wrote: 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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Cheers, Paul - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
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 rwhee...@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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
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 rwhee...@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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
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 rwhee...@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, rand...@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.li...@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 sourcesrc/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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
Hi, if I remember correctly Kepler comes with Maven out of the box. See this chart for which Eclipse packages include Maven integration: http://www.eclipse.org/downloads/compare.php?release=kepler Personally I use the Eclipse IDE for Java Developers which comes with support for both Maven and Git. Or as Ron said you can use the Eclipse STS bundle ( http://spring.io/tools/sts), which comes with quite a few additional things too. Regards, Curtis On Thu, Oct 24, 2013 at 5:49 PM, Mark Eggers its_toas...@yahoo.com 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 rwheeler@artifact-software.**com rwhee...@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, rand...@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.li...@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 sourcesrc/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.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Trying to understand how maven finds source
On 25 October 2013 06:34, Robert Dailey rcdailey.li...@gmail.com wrote: I'm trying to understand something basic, I haven't been able to find Also, Please have a look at the freely available books at http://maven.apache.org/articles.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
