I used the mvn package command, but when I attempted to run the built JAR. After implementing some functionality, I wanted to execute a “pre-version” of the application. At the moment, I don’t even know here the JAR(s) are imported to! Maven also sets the user up with a testing framework ( junit and a test directory), so it’s been pretty easy to get things off the ground. Add a Dependency Īfter doing so, when I attempt to compile my application, Maven reaches out to a repository where the dependency is made available and it’s imported into my project. I simply add a dependency to the pom.xml file.
MAVEN INTELLIJ JAR NO MANIFEST FILE ERROR CODE
This has made importing 3rd party code into my project very easy. I do use Node.js daily and using a package.json file I can easily import and manage the dependencies (including which versions) my project uses as well as define properties of my project, such as which version it’s currently at and licensing and contact information. It enables deterministic builds and simplifies the Java build process. One of the things that I liked right off was the use of what they call Project Object Model. Even-though my small project doesn’t necessitate the need for such a tool, Maven implements many industry best practices (or at least promises to do so). So, I figured that it would be worth while to learn to use it. In that project (which gathers and analyzes economic data) I decided to use Maven. To keep current with arguably the worlds most popular programming language, I decided to use Java in a project that I’m working on in my off hours. Although I’m familiar with Java, I don’t use it day-to-day.