[JBoss JIRA] (JBIDE-22877) Update RedDeer in TP for JBT 4.4.1.AM3
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22877?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22877:
------------------------------------
We can't use a "latest" URL since the TP will break every time you publish a new CI build.
Therefore we need a "stableish" URL like the one we're currently using, http://download.jboss.org/jbosstools/neon/snapshots/updates/reddeer/1.1.0...
--
Since we're approaching GA target platform code freeze, we should have a .Final release of Red Deer 1.1 to include in the TP no later than *Aug 30*.
When do you plan to release 1.1.0.Final?
We can include a non-Final version for AM3 but I don't want to have to roll that back in case you don't hit Final in time.
> Update RedDeer in TP for JBT 4.4.1.AM3
> --------------------------------------
>
> Key: JBIDE-22877
> URL: https://issues.jboss.org/browse/JBIDE-22877
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> Due to some changes/fixes in RedDeer that we'd like to use in tests, we'd like to update the RedDeer bits in our TP.
> You can simply take the latest from http://download.jboss.org/jbosstools/neon/snapshots/builds/reddeer_master/ . Let me know if it's better for you if I copy it somewhere else using the rsync job or if this is sufficient.
> Please make sure to copy the RedDeer UI feature as well as it seems to have been missing last time: JBIDE-22857 (I'm not sure how that happened.)
> Once this is done, it should be available on the current TP within a day?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22879) JavaEE jars files are built with another java version than used for compilation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22879?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22879:
-------------------------------------
[~fbricon] Maybe we should look into this together.
> 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
> 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)
9 years, 8 months