search

spotbugs / spotbugs-maven-plugin

Maven Mojo Plug-In to generate reports based on the SpotBugs Analyzer
https://spotbugs.github.io/spotbugs-maven-plugin/
Apache License 2.0
69 stars 51 forks source link

Maven command (groupId, artifactId, etc.) #2

Closed h3xstream closed 6 years ago

h3xstream commented 6 years ago

The README state a command that doesn't work unless special alias are created. mvn com.github.spotbugs:spotbugs-maven-plugin:3.1.0-SNAPSHOT:gui

Based on the maven repository link .. I found this instance of the plugin which work.. mvn com.github.hazendaz.spotbugs:spotbugs-maven-plugin:3.1.0-RC4:findbugs

This is much longer than the previous mvn findbugs:findbugs

hazendaz commented 6 years ago

You can run with

mvn spotbugs:findbugs

or

mvn spotbugs:gui

The readme is identical other than I switched out the details from old plugin to new one. Its otherwise about as close to the old plugin as possible. I will cleanup the readme as the longer command is highly unnecessary but I will get that done on the core project first and once merged rebase over here. I'll also swap out the mojo for spotbugs as soon as I can. I'll keep this open for time being.

h3xstream commented 6 years ago

mvn spotbugs:findbugs is not possible without additional configuration.

The previous plugin was release with the org.codehaus.mojo groupId which is configured by default in Maven. http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.codehaus.mojo%22%20AND%20a%3A%22findbugs-maven-plugin%22

hazendaz commented 6 years ago

mvn spotbugs:findbugs works for me so I'm not sure I'm fully understanding the issue you are observing here. What does switch from mojo to another groupId specifically cause, can you show me some more details? There is barely anything different from the original plugin at this point as original auther has been accepting everyting so at best the only change is to switch to spotbugs:findbugs. I've confirmed this on multiple projects so I'm not understanding the core problem here.

h3xstream commented 6 years ago

My suggestion :

Bonus: Consider using a groupId that is part of the default plugin groupId. Assuming we could have the permission to deploy to any of those.

hazendaz commented 6 years ago

Can you show me your error? I'm not having the issue you are and I think you are mixing issues. The hazendaz release was prior to this being brought over here. This copy hasn't been released. The read me refers to how to run providing full naming. That is verbatim from original plugin with names changed. This runs without any of that as I indicated. Please show me what failure you are getting as I have no real clue what your issue is at the moment. I'm holding up the release specifically because of this.

Get Outlook for Androidhttps://aka.ms/ghei36

From: Philippe Arteau notifications@github.com Sent: Tuesday, August 15, 2017 3:43:24 PM To: spotbugs/spotbugs-maven-plugin Cc: Jeremy Landis; Comment Subject: Re: [spotbugs/spotbugs-maven-plugin] Maven command (groupId, artifactId, etc.) (#2)

My suggestion :

Bonus: Consider using a groupId that is part default plugin groupId.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/spotbugs/spotbugs-maven-plugin/issues/2#issuecomment-322568127, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AA7ho7o3z1ESugY_vxAimfIuWAeY8VSGks5sYfTcgaJpZM4OzyMM.

h3xstream commented 6 years ago

This copy hasn't been released.

Ah! Now everything is clear. 😄

hazendaz commented 6 years ago

This is now fixed on this repo and will be released soon.