Adding jbosstools-fuse-dev
As this is a tooling requirement and not a runtime requirement, I suspect customers might
be ok-ish with it?
If I was a customer I would be asking why. What do I get for the trouble of installing yet
another version of Java? And what do I lose?
Java 7 EOL definitely works as a motivator.
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, Tooling
JBoss by Red Hat
----- Original Message -----
From: "Nick Boldt" <nboldt(a)redhat.com>
To: external-exadel-list(a)redhat.com, "soa-tools-list"
<soa-tools-list(a)redhat.com>, "Lincoln Baxter, III"
<lincolnbaxter(a)gmail.com>
Sent: Friday, May 8, 2015 1:01:49 PM
Subject: Re: Dumping java 7 support for *running* Developer studio 8?
So, just to recap the votes for moving to Java 8 as prereq.
--
Max: yes, but must determine how users will run Java 7 annotation
processing with JDK 8 as APIs are (?) incompatible. QE to investigate.
Fred: yes, +100
Denis: yes, but need better user awareness
Alexey: yes, but need to fix JBIDE-19500
Nick: yes, 7 it's one less JVM to QE (assuming concern above resolved).
--
Votes for staying on Java 7: none so far.
--
On 05/08/2015 01:09 PM, Alexey Kazakov wrote:
On 05/08/2015 09:51 AM, Denis Golovin wrote:
> I like the Idea of moving to 1.8 but my primary concern is user
> awareness that Java 8 must be used.
>
> When eclipse with JBT is started with version < 1.8, it starts and
> does its best to work, but some bundles would not be activated,
> features would be missing and no clear indication that Java 8 is
> minimum requirement.
>
> We can use -Dosgi.requiredJavaVersion=1.8 in JBDS and use eclipse
> touch points to add that into every JBDS/JBT feature and that would
> trigger dialog below, but I am not sure it is going to be enough.
We already have an issue in JIRA:
https://issues.jboss.org/browse/JBIDE-19500 (warn/inform users running
on non-compatilbe JVMs they are loosing out on features)
The idea is to detect if the error log has unresolved JVM requirement
messages and show a dialog with a warning.
If we move to Java 8 (BTW I like this idea too) then that dialog would
be even more helpful.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com