Comments (10)
I have the same issue. My OS (Windows 10) is configured in french. I was able to workaround the issue by configuring the language like this:
<plugins>
<plugin>
<groupId>com.github.spotbugs</groupId>
<artifactId>spotbugs-maven-plugin</artifactId>
<configuration>
<jvmArgs>-Duser.language=en</jvmArgs>
</configuration>
</plugin>
</plugins>
To reproduce the error you can set "fr" instead of "en" and run "mvn install site" on a project that contains issues detected by SpotBug.
from spotbugs-maven-plugin.
I'm not very good with groovy :( I took a stab at fixing the issue. I can get the xml to generate with the xml declaration but then it fails later when running a slurper against it as the declaration tag is not allowed. As the spotbugsXml.xml is just a smaller cut of spotbugsTemp.xml, I suspect that portion of the code is actually correct. It's possible later on it must be interpretted differently.
from spotbugs-maven-plugin.
Have you tried https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#inputEncoding ?
It's also nice to have minimum project that can reproduce your problem.
from spotbugs-maven-plugin.
Yes I did, with many values (ISO-8859-1, CP1252, UTF-8, ...) and combinations with many "outputEncoding" also.
Perhaps most of projects are working in UTF-8...
from spotbugs-maven-plugin.
@LoloDigi Can you provide a sample project that causes this issue?
It is true most projects are UTF-8 as that is the universal standard. You might want to determine a specific reason why your code base wants to use a legacy character encoding. Generally I've seen that used just due to improper setup when UTF-8 was fine but certainly we should work with any and a sample will help us better isolate the issue. Thanks in advance!
from spotbugs-maven-plugin.
What do you need exactly ?
Here the content of the XML generated by spotbugs maven plugin.
`
D:\workspaceSts\courrier-project\flowbean-grc-core\target\classesC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-core\7.6.24\fm-core-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\org\slf4j\slf4j-api\1.7.25\slf4j-api-1.7.25.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-common\7.6.24\fm-common-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\commons-lang\commons-lang\2.6\commons-lang-2.6.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-basic\7.6.24\fm-basic-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-util\7.6.24\fm-util-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\org\exolab\castor\0.9.3.21-flowmind\castor-0.9.3.21-flowmind.jarC:\Users\L.GUIRAUD.m2\repository\org\apache\velocity\velocity\1.6.4\velocity-1.6.4.jarC:\Users\L.GUIRAUD.m2\repository\oro\oro\2.0.8\oro-2.0.8.jarC:\Users\L.GUIRAUD.m2\repository\commons-beanutils\commons-beanutils\1.9.2\commons-beanutils-1.9.2.jarC:\Users\L.GUIRAUD.m2\repository\commons-logging\commons-logging\99.0-does-not-exist\commons-logging-99.0-does-not-exist.jarC:\Users\L.GUIRAUD.m2\repository\javax\activation\activation\1.1\activation-1.1.jarC:\Users\L.GUIRAUD.m2\repository\commons-collections\commons-collections\3.1\commons-collections-3.1.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-gui\7.6.24\fm-gui-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\api\fm-api-interaction\7.6.24\fm-api-interaction-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-data\7.6.24\fm-data-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\com\akazi\flowmind\lib\fm-antlr\7.6.24\fm-antlr-7.6.24.jarC:\Users\L.GUIRAUD.m2\repository\org\json\json\20140107\json-20140107.jarC:\Users\L.GUIRAUD.m2\repository\com\ibm\icu\icu4j\53.1\icu4j-53.1.jarD:\workspaceSts\courrier-project\flowbean-grc-core\src\main\javaD:\workspaceSts\courrier-project\flowbean-grc-core\targetLa m�thode clone() n'appelle pas super.clone()La m�thode clone() com.digitech.flowmind.object.DiffusionObject.clone() n'appelle pas super.clone()At DiffusionObject.java:[lines 25-403]In class com.digitech.flowmind.object.DiffusionObjectIn method com.digitech.flowmind.object.DiffusionObject.clone()At DiffusionObject.java:[line 169]Bad practiceLa m�thode clone() n'appelle pas super.clone()
<p>Cette classe d�finit une m�thode <code>clone()</code> qui n'appelle pas <code>super.clone()</code>, et n'est pas finale. Si cette classe ("<i>A</i>") est �tendue par une classe fille ("<i>B</i>"), et que la classe fille <i>B</i> appelle <code>super.clone()</code>, alors il est probable que la m�thode <code>clone()</code> de <i>B</i> retournera un objet de type <i>A</i>, ce qui viole le contrat standard de <code>clone()</code>.</p>
<p>Si toutes les m�thodes <code>clone()</code> appellent <code>super.clone()</code>, elles ont alors la garantie d'utiliser <code>Object.clone()</code>, qui retourne toujours un objet du type correct.</p>
I put a screenshot for the 'real' display in my intellij. And as text for all the content :
from spotbugs-maven-plugin.
A small sample project that also has the issue, simple hello world will do.
from spotbugs-maven-plugin.
@jflecomte Thanks, I'll take a deeper look as soon as I can.
from spotbugs-maven-plugin.
@jflecomte The workaround is working great.
Thank you for your support !
from spotbugs-maven-plugin.
Issue resolved and will be available in plugin for spotbugs 4.0.0.
from spotbugs-maven-plugin.
Related Issues (20)
- Extraneous "following classes needed for analysis were missing" message introduced in 4.7.3.1? HOT 3
- SuppressFBWarnings is ignored HOT 10
- spotbugs:gui not working HOT 3
- Extend via dependencies rather than custom configuration HOT 8
- Uses deprecated maven components HOT 8
- Does spotbugs report plugin support aggregation HOT 2
- Review replacing usage of 'ant'
- FindBugsAntBuildLogic 3.7 generates invalid findbugs_report.xml file HOT 2
- java 22 support will be in groovy 4.0.16 which isn't out yet HOT 2
- plugin build setting HOT 8
- makeConcatWithConstants + apply classes needed for analysis were missing HOT 1
- check does not fail if called as defaultGoal of profile HOT 4
- Build repeats "Unable to create Maven project for" warning and fails HOT 5
- NOTICE: Maven support will be moved to 3.6.3 as minimum on next release
- Sporadic spotbugs failure
- Spotbugs Maven Plugin 4.8.4 waiting on groovy! HOT 1
- Support the `chooseVisitors` option
- Is there a way to configure an accepted number of errors in order to introduce spotbugs into existing projects HOT 2
- All documentation descriptions are empty HOT 1
- After recent updates in core libraries ad plugin `verify` and `spotbugs:check` works differently
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spotbugs-maven-plugin.