]
Matej Briskar commented on FORGE-1698:
--------------------------------------
Isn't this already implemented?
(
MavenJavaCompilerFacet should use user properties instead of
declaring the compiler plugin
------------------------------------------------------------------------------------------
Key: FORGE-1698
URL:
https://issues.jboss.org/browse/FORGE-1698
Project: Forge
Issue Type: Enhancement
Components: Build Tools - Maven
Affects Versions: 2.3.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Priority: Minor
Labels: Starter
Fix For: 2.4.1.Final
The current {{org.jboss.forge.addon.maven.projects.facets.MavenJavaCompilerFacet}}
declares a compiler plugin with the parameters:
{code}
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
{code}
As per
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html, this
could be changed to:
{code}
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
</properties>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: