-
Bug
-
Resolution: Obsolete
-
Low (View bug fix roadmap)
-
None
-
5.8.4
-
None
-
5.08
-
The version of the maven-compiler-plugin GreenHopper uses (2.0.2) doesn't define a default encoding to use with the java compiler, and will therefore be using the platform default which can cause issues.
- is related to
-
JRASERVER-26744 JIRA doesn't set the encoding when using the maven-compiler-plugin
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-4358] GreenHopper doesn't set the encoding when using the maven-compiler-plugin
We still have this definition:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.4</version>
<configuration>
<source>1.6</source>
<target>1.6</target>
<encoding>${project.build.sourceEncoding}</encoding>
<!-- this is the default in version 2.3.2 of the plugin, but for now we're using version 2.0.2 -->
<maxmem>512m</maxmem>
</configuration>
</plugin>
Should we just remove it?
mtokar this probably is not an issue anymore. Esp. that IIRC I already applied a fix. If you guys upgraded your parent POM "recently" and do not override the maven-compiler-plugin version then it should be all good.
You should be able to remove the encoding part of the configuration, but don't remove the plugin definition. I've checked and you guys are still on an old version of the parent (closed source) pom, version 25. You should probably consider updating to a later version, which would allow you to remove some cruft in your own poms. Note that updating might not be as trivial as one thinks...