You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue is not with Groovy per se, it is with Ant, which this mojo explicitly uses to run SpotBugs for some reason (merely using a Groovy utility to prepare the Ant usage). I filed https://github.com/apache/ant/pull/200 to deal with this upstream, though it would be better to drop the Ant dependency and either fork via `ProcessBuilder` or directly run the SpotBugs entry point class.
As far as I can tell the workaround is just to configure the mojo to fork—there is no need to set any special JVM arguments, since the System.setSecurityManager call is only used inside the Maven JVM when fork is false.
The text was updated successfully, but these errors were encountered:
hazendaz
changed the title
The issue is not with Groovy per se, it is with Ant, which this mojo explicitly uses to run SpotBugs for some reason (merely using a Groovy utility to prepare the Ant usage). I filed https://github.com/apache/ant/pull/200 to deal with this upstream, though it would be better to drop the Ant dependency and either fork via ProcessBuilder or directly run the SpotBugs entry point class.
Review replacing usage of 'ant'
Aug 26, 2023
As far as I can tell the workaround is just to configure the mojo to
fork
—there is no need to set any special JVM arguments, since theSystem.setSecurityManager
call is only used inside the Maven JVM whenfork
isfalse
.Originally posted by @jglick in #423 (comment)
The text was updated successfully, but these errors were encountered: