[
https://jira.jboss.org/jira/browse/JBWS-2818?page=com.atlassian.jira.plug...
]
Alexandros Karypidis commented on JBWS-2818:
--------------------------------------------
Guys,
I looked up the Maven docs and see that it only sets ${java.home} to point to the JRE (not
JDK) home (see
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide).
As far as I understand, ${java.jdk15.home} is a special variable that the user should set
in their profile. Now, setting that variable simply allows one to point to the use of a
specific JDK installation, in case a JDK 1.6 is dected by maven (the profile declaration
becomes active when using JDK 1.6 anyway - see <activation> tag), while at the same
time setting a compiler java version to 1.5. The more straight-forward way to do that is
to set JAVA_HOME prior to invoking maven.
I figure it can be safely removed. For example, I can see that JBossWS-CXF does not have
such a declaration.
Native stack compliation error on Windows with JDK1.6
-----------------------------------------------------
Key: JBWS-2818
URL:
https://jira.jboss.org/jira/browse/JBWS-2818
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: jbossws-native
Reporter: Jim Ma
Assignee: Jim Ma
Fix For: jbossws-native-3.2.2
The jdk1.6 profile will cause complication error:
<profile>
<id>jdk16</id>
<activation>
<jdk>1.6</jdk>
</activation>
<build>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<compilerVersion>1.5</compilerVersion>
<executable>${java.jdk15.home}/bin/javac</executable>
<fork>true</fork>
</configuration>
</plugin>
</plugins>
</build>
</profile>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira