Download Simple Maven Project
Tristan Ridings
The pom.xml file is the core of a project's configuration in Maven. It is a single configuration file that contains the majority of information required to build a project in just the way you want. The POM is huge and can be daunting in its complexity, but it is not necessary to understand all of the intricacies just yet to use it effectively. This project's POM is:
You executed the Maven goal archetype:generate, and passed in various parameters to that goal. The prefix archetype is the plugin that provides the goal. If you are familiar with Ant, you may conceive of this as similar to a task. This archetype:generate goal created a simple project based upon a maven-archetype-quickstart archetype. Suffice it to say for now that a plugin is a collection of goals with a general common purpose. For example the jboss-maven-plugin, whose purpose is "deal with various jboss items".
By default your version of Maven might use an old version of the maven-compiler-plugin that is not compatible with Java 9 or later versions. To target Java 9 or later, you should at least use version 3.6.0 of the maven-compiler-plugin and set the maven.compiler.release property to the Java release you are targetting (e.g. 9, 10, 11, 12, etc.).
Phases are actually mapped to underlying goals. The specific goals executed per phase is dependant upon the packaging type of the project. For example, package executes jar:jar if the project type is a JAR, and war:war if the project type is - you guessed it - a WAR.
INFO: You might like to consider using the Maven wrapper to insulate your developers against having the correct version of Maven, or having to install it at all. Projects downloaded from Spring Initializr have the wrapper included. It shows up as a script mvnw in the top level of your project which you run in place of mvn.
The simple Hello World sample is completely self-contained and does not depend on any additional libraries. Most applications, however, depend on external libraries to handle common and complex functionality.
This block of XML declares a list of dependencies for the project. Specifically, it declares a single dependency for the Joda Time library. Within the element, the dependency coordinates are defined by three sub-elements:
Am I missing something?
Is it because of the archetype I'm starting with?
When I tried to start a Maven project without an archetype, I didn't get pom.xml.
Is there a better archetype for my purposes?
Now go to the current directory from where you have executed the mvn command. For example: C:\Users\SSS IT\CubeGenerator. You will see that a simple java project is created that has the following directory:
I use the last version of Eclipse, Mars 4.5.2, so it already contains a new version Maven plugin. From -creating-archetypes.html, the firt step is "1. Create a new project and pom.xml for the archetype artifact". However, I cannot even create a very, very simple Maven project after trying various most all basic ways, as illustrated below.
At here, it's forced to click one of the group ids and then click 'Next' to create a maven project. I choose the first one, named 'maven.archetype.archetype', (and tried most of them listed on the image as well), then click next:
My goal is not creating a Maven project. I already created a GWT web project which was implemented and run smoothly without Maven. I'd like to build a GWT REST application by following the steps in -rest-app.html#.V1IdrPl96M9 and create Java REST API which takes input through url and returns result, achieving the same functionality of my UI. When following ronanquillevere's guide, I am stuck at Maven as one image in -rest-app.html#.V1IdrPl96M9
I will get a short list of achetypes only from org.apache.maven.archetypes groupId. The good ones for starting is maven-archetype-quickstart and maven-archetype-webapp like my predecessors said.
When you do a mvn archetype:generate, a default selection appears in enclosing curly brackets (), e.g. (1274), if you scroll up to see what #1274 is, it is usually the default Java archetype to try out or start out with, if doing simple Java projects, so is safe to select.
You may want to consider Java Archetype: it has reasonable defaults for quickly starting a Java project following best practices, including JUnit tests. I conceived it as a modern successor of maven-archetype-quickstart.
In order to join efforts if possible and avoid wasteful duplication, I actively searched for other archetypes that would have the same aim as mine: provide a simple archetype with reasonable defaults to easily start a modern Java project. (This was mostly done around June 2020.)
A general search on the internet led me to The Practical Developer. When contacted, he wrote to me (by e-mail) that he does not work on his archetype regularly and therefore preferred to decline collaborating on such a project.
As searches on the net did not reveal other useful results, and as I found no specialised search tool suitable for my needs, I implemented a simple archetype browser. It lists all the archetypes available in Maven Central. There are far too many to review manually, thus, I selected those whose groupId and artifactId existed since at least three years and have been updated during the last year, in hope of finding projects that are maintained on the long run, which I suppose indicates more probably a good quality project. (Of course this filter may have missed good quality archetypes that perfectly match the stated goal; I have no way to know. As a case in point, this very archetype does not pass that filter as I have changed its artifactId over time.)
Load that first change to the POM. In IntelliJ, look for the little floating windoid with the blue M logo. Click that logo. Otherwise, open the Maven panel within IntelliJ. Click the first icon for Reload all Maven projects.
Errors running builder 'Maven Project Builder' on project 'TestApp'.Could not calculate build plan: Plugin org.apache.maven.plugins:maven-resources-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-resources-plugin:jar:2.6
This is the very minimum pom.xml content you need. If you have this then the something else should be the problem. You don't need more than this to build a simple basic maven project. I think closing tag is missing the the code you posted
Error was thrown Because it was unable to download any artifacts or resources from repo.Reason was i was behind the proxy i needed to configure in settings.xml
Located in
pref-> maven -> user settings
After i configured everything working fine
true http proxy.somewhere.com 80
If you are using Eclipse, then while creating a maven project from wizard it will give one check box on top which says "Create a simple maven project.........". You can select this if you are confuse with what type to select
You may want to consider java-archetype: it has reasonable defaults for quickly starting a Java project following best practices. It can be considered a modern successor of maven-archetype-quickstart.
The demo shows the relationship between the dependencies and the Eclipse. When a Maven project is selected, all such dependencies are automatically downloaded. If any dependencies are not present, Eclipse will show errors.
Not only did we go over the basics of Maven in this tutorial, but we also covered how to create a basic Maven project in Eclipse. We learned how to create a Maven project from scratch and what steps to keep in mind. We saw the relationship between the dependencies and how a Maven project works in Eclipse.
You should be able to use mvn archetype:generate. You can choose, e.g., org.scala-tools.archetypes:scala-archetype-simple. You need to put in the number number next to the archetype name in the output of your mvn archetype:generate command because the numbering can change over time. There are also other options like eu.stratosphere:quickstart-scala as documented in this article.
I created two most simple eclipse maven projects, one is test1, and the other is test2.
Project test1 contains just a 'say hello' static main method in it's only class Main.java.
Project test2 contains also nothing but a static main method invoking test1's 'say hello' method, in its only class Main.java.
Of cause, in Project test2's pom.xml, declares a dependency on test1.That's it!
Sure I can build project test1 successfully with 'maven clean package', and run OK.
But when I tried to build test2 with 'maven clean package', it gave out error:
I know if I run 'mvn install' with Test1, everything would be OK, but I just do NOT want to install Test1 into local maven repository, I want to make it dependable in local workspace, how can I do that? Anything wrong with me?
The Eclipse Maven plugin m2e has a feature called "Workspace Resolution". If you enable it, you can directly use the results of other projects in the workspace. You can see that it works if you open the "Maven Dependencies" folder in your Eclipse project. There, you can see a folder symbol in front of the other project (instead of the usual binary symbol for other jars).
df19127ead