-
Notifications
You must be signed in to change notification settings - Fork 53
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
Support for classifier configuration of Plugin artifact #23
Comments
@gleclaire Hi, I was wondering if you could take a look at this issue. |
I have temporary fix that might not be ideal for end-users .. but good enough for me: The <plugin>
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
<version>3.1.1</version>
<configuration>
<fork>false</fork>
<timeout>9999999</timeout>
<effort>Max</effort>
<threshold>Low</threshold>
<failOnError>true</failOnError>
<includeFilterFile>${session.executionRootDirectory}/findbugs-security-include.xml</includeFilterFile>
<excludeFilterFile>${session.executionRootDirectory}/findbugs-security-exclude.xml</excludeFilterFile>
<plugins>
<plugin>
<groupId>com.h3xstream.findsecbugs</groupId>
<artifactId>experimental-plugin</artifactId>
<!--<classifier>jar-with-dependencies</classifier>--> <!-- Not supported yet -->
<version>1.8.0</version>
</plugin>
</plugins>
</configuration>
<dependencies>
<dependency>
[...]
<!-- List of dependencies goes here -->
</dependency>
</dependencies>
</plugin> |
@h3xstream Not tested but have added classifier support for next release. |
I need to bundle dependencies with a SpotBugs plugin. The easiest way to publish this plugin is releasing the normal jar and a jar with all the needed dependencies.
My small obstacle is that I can't configure a classifier in the PluginArtifact XML section.
spotbugs-maven-plugin/src/main/groovy/org/codehaus/mojo/spotbugs/SpotBugsMojo.groovy
Lines 1179 to 1183 in 263bbd0
Maybe I'm missing something regarding Plugin Artifact dependencies and the all-in-one jar is not necessary.
The text was updated successfully, but these errors were encountered: