[
https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-22879:
-------------------------------------
Unfortunately, this will remain targeted to later, since it is an upstream bug. Please see
the linked bugzilla if you wish to provide further input there.
It's worth noting, however, that this bug is almost entirely cosmetic. We recognize
that people may depend on the manifest flag for debugging purposes, however, exporting and
publishing of projects is generally not intended for production purposes. These are
development tools, meant to speed up rapid development and testing on various application
servers.
For real deployments, it's suggested to use your actual maven build for repeatable and
accurate results.
JavaEE jars files are built with another java version than used for
compilation
-------------------------------------------------------------------------------
Key: JBIDE-22879
URL:
https://issues.jboss.org/browse/JBIDE-22879
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.3.Final, 4.4.0.Final
Environment: I've observed this problem on a Win7 64 bit machine with Oracle
JRE 1.8.0_102 64 bit. It was present in both JBoss Developer Studio 8.1.0.GA and 10.0.0.GA
when used in conjunction with embedded Maven installation and JBoss EAP 6.4 target
runtime.
Reporter: Mikhail Kalkov
Assignee: Rob Stryker
Fix For: LATER
Attachments: test-projects.zip
I have installed system-wide JRE 8 in order to run all java applications with it. At the
same time, out target platform is still based on Java 7 and that's why I've also
downloaded JDK 7 and set JAVA_HOME path to it.
When I build test-ejb project from attached zip file on command line, maven both compiles
and packages it with JDK 7 obtained from JAVA_HOME. When I build the same project with
JBoss Developer Studio which was configured via Window > Preferences > Java >
Installed JREs to use JDK 7 by default, class files get version 51 (java 7) but Build-Jdk
stanza in MANIFEST.MF is set to 1.8.0_102 instead of 1.7. I've also observed that
test-ear project is also packaged with Java 8 instead of Java 7.
This is not a big issue but is a bit worrying since for example jar tool from JDK 8 may
contains bugfixes not present in JDK 7. This also makes me think that other tools may be
fetched from wrong JDK version. Finally, I'm not even sure whether this is a JBoss
Tools, Eclipse WTP or Eclipse M2E issue but it is clearly present in the latest stock
version of JBoss Developer Studio.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)