This functionality has been added to version 1.6 of the maven-shade-plugin (just released). minimizeJar will now not remove classes that have been specifically included with filters. Note that including some of an artifact’s classes in a filter will exclude non-specified classes for that artifact, so be sure to include all the classes that you need. … Read more
After some research, I felt it looked like some version incompatibility. and indeed, it is, between the maven version I am using to build the applications using the plugin, and the maven core version used in the plugin. in my plugin, I was using latest maven core version available as a dependency, ie 3.5.2 I … Read more
Currently, openapi-generator doesn’t support oneOf. This is a capability that had been newly introduced with OpenAPI v3 (FYI, only v2 and below are called “Swagger”, it has then been renamed to OpenAPI). There are various generators (Java, Spring, lots of other languages). I have seen that contributions have been made during this year to enable … Read more
Figured it out using the maven-war-plugin. See the configuration below: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-war-plugin</artifactId> <version>2.1.1</version> <configuration> <archive> <manifestEntries> <version>${project.version}</version> </manifestEntries> </archive> </configuration> </plugin>
Remove <filtering>true</filtering>, it corrupts the jar files.
Two ways to pass command line arguments into mvn:exec: Method 1, on the command line: mvn exec:java -Dexec.mainClass=”com.myPackage.myClass” -Dexec.args=”command line arguments” Method 2, in the maven POM file: <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <configuration> <mainClass>com.myPackage.myClass</mainClass> <commandlineArgs>command line arguments</commandlineArgs> </configuration> </plugin> </plugins> </build> Then on the command line all you have to do is run: mvn … Read more
Recently I faced the same exception. After a bit researching I found that maven-compat plugin solves the problem: <dependency> <groupId>org.apache.maven</groupId> <artifactId>maven-compat</artifactId> <version>3.0.5</version> <scope>test</scope> </dependency>
The copy goal is more appropriate here and it lets you specify an output directory as well (which is deprecated in the get goal): mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:copy -Dartifact=groupId:artifactId:version[:packaging][:classifier] -DoutputDirectory=[target] -Dmdep.useBaseVersion=true mdep.useBaseVersion=true will remove timestamps from snapshot builds.
There is now a work-in-progress implementation of annotations for Maven plugins developments! Read the following links: https://cwiki.apache.org/confluence/display/MAVEN/Java+5+Annotations+for+Plugins http://olamy.blogspot.fr/2012/05/java5-annotations-support-for-maven.html
It’s a new feature to warn you that some plugin you are using may not work in future. You can make a lot quieter by using the brief mode, though it never goes away completely. mvn package -Dmaven.plugin.validation=brief You can set this in the MAVEN_ARGS environment variable and have it picked up everywhere, so apart … Read more