Skip to content
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

spotbugs or findsecbugs create directory in target which it shouldnt #34

Closed
nimaj94 opened this issue Mar 6, 2018 · 2 comments · Fixed by #238
Closed

spotbugs or findsecbugs create directory in target which it shouldnt #34

nimaj94 opened this issue Mar 6, 2018 · 2 comments · Fixed by #238

Comments

@nimaj94
Copy link

nimaj94 commented Mar 6, 2018

I am currently using spotbugs and i use it using maven, so i put these lines in my pom in reporting plugins

<plugin>
<groupId>com.github.spotbugs</groupId>
  <artifactId>spotbugs-maven-plugin</artifactId>
  <version>3.1.1</version>
<configuration>
<plugins>
<plugin>
<groupId>com.h3xstream.findsecbugs</groupId>
<artifactId>findsecbugs-plugin</artifactId>
<version>LATEST</version>
<!-- Auto-update to the latest stable -->
</plugin>
</plugins>
</configuration>
</plugin>

but there is a problem.
when i execute site:site it create some directory inside my target folder.
the directory is
C_\Users\ [myUserName] \ .m2\repository\com\h3xstream\findsecbugs\findsecbugs-plugin\1.7.1
and findsecbugs-plugin-1.7.1.jar is inside this directory.
like it should be
C:\Users\ [myUserName] \ .m2\repository\com\h3xstream\findsecbugs\findsecbugs-plugin\1.7.1
but somebody accidentally use '_' instead of ':' .

@hazendaz
Copy link
Member

hazendaz commented May 3, 2018

spotbugs maven plugin creates this due to underlying groovy usage. I'm unsure how to fix it but see the issue is duplicating files all over.

@hazendaz
Copy link
Member

hazendaz commented Jan 3, 2021

This original issue was handling that was missing with windows that was present for linux style line endings. The original fix put in actually broke things so this is sort of an issue still. I think copying the jars to target is unnecessary as they won't change during the run However, for time being to get folks running again the original issue here of deeply nested is gone. The jar files in question will still be added to target. Opening new issue and will flag it back to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants