-
Notifications
You must be signed in to change notification settings - Fork 1
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
Error assembling JAR: Manifest file does exist #51
Comments
Hello! Just noticing this ticket today. Sorry for the delay! It's certainly possible to do that, but I'd personally avoid it because creating an empty jar file is something you'd normally want to prevent in a build. As I mentioned in the blog:
|
Not a bug, more a remark on the blog post at https://blog.io7m.com/2019/05/16/instant-code-reloading.xhtml
In this post you refer to the un-existing manifest file in a parent pom. Instead of creating this file, it is also possible to setup the jar plugin and add the skipIfEmpty configuration to the execution.
<execution> <id>jar</id> <goals> <goal>jar</goal> </goals> <configuration> <skipIfEmpty>true</skipIfEmpty> </configuration> </execution>
The text was updated successfully, but these errors were encountered: