It sounds like you have got yourself a bit tangled up.
If you are using maven you do not need to download and extract anything, maven will deal with dependencies for you and download any packages required. The important thing with maven is to ensure that your directory structure is correct as maven expects certain things in certain locations. You can override the default directory locations, but I would advise strongly against it. It makes your POM more complicated and anybody else used to maven who looks at your project will not find things in the location they are expecting to find things.
Have a look here for maven directory structure:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
I would suggest you do the following:
1. Create a new root directory for your project.
2. Create your POM file in this directory (pom.xml)
3. Create the src/main/java directory structure
4. In the java directory create your first java class
Once you have done this perform a:
“mvn clean install –U”
This will download all of the dependencies that you require from the maven central repo and build your project for you. You don’t need to manually download or extract anything maven will do it all for you.
Even though you are using Maven it is still a Java project. Maven at its most basic is a dependency management/build system that was originally designed to be used with Java, but you can use it with others things as well (e.g. scala). For more info have a look at http://maven.apache.org/what-is-maven.html.
I’m not an Eclipse user and not a big fan of Eclipse, so I may well be biased with this recommendation, but I would suggest using an IDE that supports POM files out of the box like IntelliJ IDEA, or even Netbeans. My personal preference is IntelliJ IDEA which has some excellent GIT support in the latest version:
http://www.jetbrains.com/idea/download/
You can then just open your POM file with the IDE and it will load the maven project into the IDE for you, no configuration of a maven plugin, no running IDE specific maven commands, no faffing, it will just work.
I have really just scratched the surface, but hopefully there is enough above to get you going.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.
It’s asking you to select the Java SDK to use with your project.
Assuming IntelliJ IDEA 11:
Click File -> Project Structure…
Select 1.7 in the drop down box under project SDK: (Default will be <No SDK>)
Click OK
If you have created the basic maven structure suggested below all you need to do is open the POM with intelliJ IDEA, it will then create the IDEA project structure for you automatically.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/h8UB6j4tb2AJ.
I disagree, generally speaking you are going to need to start using ANT and/or Maven in the future when you want to plug your tests into CI, or run them using a cron job/scheduled task anyway. Bearing this in mind why not start learning ANT/Maven at the outset? It will affect your decisions on how to build your test framework and even though it’s a slightly higher learning curve to begin with it will pay huge dividends in the long run.
I agree that Maven with Eclipse is a black art as Eclipse doesn’t support Maven out of the box (Personally I’m not a big fan of Eclipse anyway) which is why I would always recommend a IDE that supports maven out of the box to make your life easy whilst starting up.
The big positive for maven in my mind is that it controls all of the dependency management and classpath settings for you so once you have a basic POM you don’t need to worry about it.
I’ve worked with a lot of people who have had real problems with various jars, jar versions, the classpath and general projects structure. Maven generally fixes all of these problems by forcing a sane project structure upon you and dealing with dependencies and classpaths so you don’t have to worry about it.
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/5an71Sv8Im8J.