-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no main manifest in jars #67
Comments
Maven is a build system. mvn clean package/install is not supposed to Please read the guide and use mvn assembly:assembly. cheers Please excuse if short or if it does not make any sense. Sent via my phone On 29.06.2013, at 17:22, Maurice de Rooij notifications@github.com wrote: After compiling the maven file in the root of the project on Windows XP, Tried compiling with both mvn clean install and mvn clean package. — |
Your dev guide tells to use mvn clean install Additionally, isn't maven supposed to do just that, building runnable jars using maven-jar-plugin without additional assembly:assembly? |
The dev guide states both things - how to build and how to create an executable jar. "In order to package the command line app into an executable jar, navigate to the cmd project and run mvn Also, no. Maven is not supposed to do just that. As I said maven is a build system and is supposed to generate packages that can be resolved automatically and used by other developers in their projects. The maven jar plugin is just one of many plugins that extends the core functionality of maven and allows you create different jars with more complex structures - so does the maven assembly plugin, which I use. If you read the maven lifecycle here: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html, |
I am closing this issue now. |
After compiling the maven file in the root of the project on Windows XP, all jars fail to run, exiting with the message 'no main manifest attribute'.
Tried compiling with both
mvn clean install
andmvn clean package
.The text was updated successfully, but these errors were encountered: