Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
On Wed, Mar 4, 2015 at 5:42 PM, Igor Fedorenko i...@ifedorenko.com wrote: This is getting off-topic, but I think we should plan to move to java 8 for the next release after mars. +1 -- Regards, Igor On 2015-03-04 11:32, Konstantin Komissarchik wrote: What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the “no further public updates” phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _/cannot/_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin *From:*cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Ed Willink *Sent:* Wednesday, March 04, 2015 6:57 AM *To:* cross-project-issues-dev@eclipse.org *Subject:* Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk mailto:e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.org mailto:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues- d...@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Geschäftsführer vogella GmbH Haindaalwisch 17a, 22395 Hamburg Amtsgericht Hamburg: HRB 127058 Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel USt-IdNr.: DE284122352 Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: http://www.vogella.com ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
- Original Message - From: Ed Willink e...@willink.me.uk To: cross-project-issues-dev@eclipse.org Sent: Thursday, March 5, 2015 9:17:25 AM Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi I think that this thread is about both. Nobody has advanced a strong argument for retaining Java 6 support, so we can move on without upsetting anybody. Doug: if you examine the tabulated per-plugin BREEs in the platform project plan you will see a clear indication that jdt.core is 1.6. (The only 1.7 is the filesystem.java7 bundle.) The table with BREEs is generated by a script few times per release cycle. This is work in progress towards what will become Mars platform. This table is not the plan for BREE per bundle it's for information purposes once it's released. In the final stages this table will be regenerated and be 100% accurate. Alexander Kurtakov Red Hat Eclipse team Therefore IMHO this change should have been announced: a) because it was a change to the platform project plan b) because it clearly has an impact on many other projects Regards Ed Willink On 05/03/2015 01:02, Ian Bull wrote: Is this thread about what minimum BREE to use, or is it about announcing changes to this? I agree with most people here that Java 7 is a sensible minimum BREE for Mars, but I get the sense that this thread was more about how / where these changes are announced. Cheers, Ian On Wed, Mar 4, 2015 at 2:36 PM, Gunnar Wagenknecht gun...@wagenknecht.org wrote: Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org : On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. And we have a solution for this too -- LTS. If someone wants support for Eclipse for an older version of Java, then LTS would be the obvious recommendation. :) I guess we just need to come up with a common definition of what we mean by current version. I say: it should be every version receiving security updates public and free accessible for the community (committers, contributors and users). As of May 2015, Java 7 will fall out of that list. But that's just my two cents. -Gunnar ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9227 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi Ed We always publish our plan and all updates to the 'eclipse-dev' list. The next plan update will be for M6. You can also follow the plan update discussions in the corresponding plan update bugzillas in the Platform PMC component. The one for M6 is https://bugs.eclipse.org/458730. As Alex mentioned, that will also update the appendix with the BREEs. Note that besides the supported target environments of the Platform, there is usually also a discussion what the lowest JRE is for the packages (EPPs). This is decided by the package maintainers. For Luna most were already requiring JRE 7. As for why we didn't send a note, simply because we changed bundle BREEs many times in the past years without ever announcing it. Sorry if this caused any troubles for you! Dani From: Ed Willink e...@willink.me.uk To: cross-project-issues-dev@eclipse.org Date: 05.03.2015 08:17 Subject:Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by:cross-project-issues-dev-boun...@eclipse.org Hi I think that this thread is about both. Nobody has advanced a strong argument for retaining Java 6 support, so we can move on without upsetting anybody. Doug: if you examine the tabulated per-plugin BREEs in the platform project plan you will see a clear indication that jdt.core is 1.6. (The only 1.7 is the filesystem.java7 bundle.) Therefore IMHO this change should have been announced: a) because it was a change to the platform project plan b) because it clearly has an impact on many other projects Regards Ed Willink On 05/03/2015 01:02, Ian Bull wrote: Is this thread about what minimum BREE to use, or is it about announcing changes to this? I agree with most people here that Java 7 is a sensible minimum BREE for Mars, but I get the sense that this thread was more about how / where these changes are announced. Cheers, Ian On Wed, Mar 4, 2015 at 2:36 PM, Gunnar Wagenknecht gun...@wagenknecht.org wrote: Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this ?end of public updates? date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. And we have a solution for this too -- LTS. If someone wants support for Eclipse for an older version of Java, then LTS would be the obvious recommendation. :) I guess we just need to come up with a common definition of what we mean by current version. I say: it should be every version receiving security updates public and free accessible for the community (committers, contributors and users). As of May 2015, Java 7 will fall out of that list. But that's just my two cents. -Gunnar ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9227 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
eclipse.platform.debug and eclipse.platform.ant has been moved from 1.6 to 1.7 BREE eclipse.jdt.debug will be moving from 1.5 to 1.7 BREE shortly. Sarika From: cross-project-issues-dev-requ...@eclipse.org To: cross-project-issues-dev@eclipse.org Date: 03/05/2015 03:27 PM Subject:cross-project-issues-dev Digest, Vol 110, Issue 10 Sent by:cross-project-issues-dev-boun...@eclipse.org Send cross-project-issues-dev mailing list submissions to cross-project-issues-dev@eclipse.org To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev or, via email, send a message with subject or body 'help' to cross-project-issues-dev-requ...@eclipse.org You can reach the person managing the list at cross-project-issues-dev-ow...@eclipse.org When replying, please edit your Subject line so it is more specific than Re: Contents of cross-project-issues-dev digest... Today's Topics: 1. Re: Update site time outs (Ed Merks) 2. Re: jdt.core move to Java 7 BREE (Aleksandar Kurtakov) 3. Re: jdt.core move to Java 7 BREE (Aleksandar Kurtakov) 4. Re: jdt.core move to Java 7 BREE (Daniel Megert) -- Message: 1 Date: Thu, 05 Mar 2015 08:53:57 +0100 From: Ed Merks ed.me...@gmail.com To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] Update site time outs Message-ID: 54f80b95.7030...@gmail.com Content-Type: text/plain; charset=windows-1252; Format=flowed Camille, The download server has been maxed out all week with HTTP connections at between 9,000 to 12,000 for download1, which I assume is the primary server for http:/download.eclipse.org: https://dev.eclipse.org/committers/help/status.php Things like http://download.eclipse.org/releases/luna/201501121000/content.jar were taking often more than 4 minutes to download. Today it's finally at a more reasonable level at less than 3,000 when I used it early in the morning in Europe and I am able to work effectively again. Some of these problems seem to be to be fundamentally p2 problems. Eike and I looked very closely at the underlying infrastructure as part of the Oomph work and even added offline support for Oomph as a layer on top, but p2 itself has a habit of downloading content and artifact files (not to mention the artifacts themselves when not using bundle pool) over and over again. Also p2 tries many combinations for different potential update site configurations many of which yield 404. In the end, it's very annoying to wait for the same things to download again and again and when large numbers of users are all doing that at the same time, failing, and trying again, it becomes a serious server problem. Regards, Ed On 04/03/2015 4:33 PM, LETAVERNIER Camille wrote: Hi, We?ve received several notifications [1] from users who encounter a lot of ?Read time out? when they are trying to install/update some components from the simrel (/releases/luna) update site. It seems that it is a general issue (not specific to Papyrus). The same thing happens on the mars simrel update site (/releases/mars) Are there some known server/performances issues? Maybe related to the recent SR2 release? Did anyone else run into these issues? [1] https://www.eclipse.org/forums/index.php/t/1025771/ https://www.eclipse.org/forums/index.php/t/1025771/ Camille ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- next part -- An HTML attachment was scrubbed... URL: https://dev.eclipse.org/mailman/private/cross-project-issues-dev/attachments/20150305/adeb73a6/attachment.html -- Message: 2 Date: Thu, 5 Mar 2015 02:55:53 -0500 (EST) From: Aleksandar Kurtakov akurt...@redhat.com To: Cross project issues cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Message-ID: 686168366.23266320.1425542153656.javamail.zim...@redhat.com Content-Type: text/plain; charset=utf-8 - Original Message - From: Gunnar Wagenknecht gun...@wagenknecht.org To: Mike Milinkovich mike.milinkov...@eclipse.org, Cross project issues cross-project-issues-dev@eclipse.org Sent: Thursday, March 5, 2015 12:36:30 AM Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this ?end of public updates? date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Just to chime in here: For me there are no need to keep jdt.core BREE on Java6 unless it does not allow to build Java 6 projects. If all features for targeting Java 6 continues to work (i.e. Java 6 annotation processing) then requiring to run the IDE with Java 7 is a much smaller if even existing issue. /max Hey! I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Cheers, -Martin Am 04.03.2015 um 20:34 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 12:18 PM, Ed Willink wrote: But As stated above, we expect that Eclipse works fine on other current Java VM and OS versions But Java 6 is not a current version of Java. It was EOL'd in 2013. See http://www.oracle.com/technetwork/java/eol-135779.html -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 (mobile) 100x130.jpg ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev /max http://about.me/maxandersen ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi (I would love it if Mars required Java 8, since I like @NonNull annotations and the Java 7 compatibility is really troublesome.) However I am keen that my project follows the Eclipse consensus, which does not seem to exist. My Hudson builds now fail so I need to know where the new consensus is. Regards Ed Willink On 04/03/2015 16:32, Konstantin Komissarchik wrote: What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the “no further public updates” phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _/cannot/_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin *From:*cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Ed Willink *Sent:* Wednesday, March 04, 2015 6:57 AM *To:* cross-project-issues-dev@eclipse.org *Subject:* Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk mailto:e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.org mailto:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the no further public updates phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _cannot_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin From: cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed Willink Sent: Wednesday, March 04, 2015 6:57 AM To: cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From:Ed Willink mailto:e...@willink.me.uk e...@willink.me.uk To:Cross project issues mailto:cross-project-issues-dev@eclipse.org cross-project-issues-dev@eclipse.org Date:04.03.2015 15:27 Subject:[cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by:cross-project-issues-dev-boun...@eclipse.org _ Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
This is getting off-topic, but I think we should plan to move to java 8 for the next release after mars. If we start talking about this now and announce this as part of mars release, I think this gives users plenty of time to prepare and less excuse for grumbling (although I imagine there still be some grumbling). -- Regards, Igor On 2015-03-04 11:32, Konstantin Komissarchik wrote: What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the “no further public updates” phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _/cannot/_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin *From:*cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Ed Willink *Sent:* Wednesday, March 04, 2015 6:57 AM *To:* cross-project-issues-dev@eclipse.org *Subject:* Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk mailto:e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.org mailto:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Our consensus has always been to not have a consensus. Each project moved to where they needed to be when they needed to be. Obviously the decisions of other projects affect yours, particularly the platform. And for that, I go by their project plan which has no mention of JRE 6 for Mars. https://www.eclipse.org/projects/project-plan.php?planurl=/eclipse/development/plans/eclipse_project_plan_4_5.xml Doug. From: Ed Willink e...@willink.me.ukmailto:e...@willink.me.uk Reply-To: Cross project issues cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Date: Wednesday, March 4, 2015 at 11:46 AM To: cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi (I would love it if Mars required Java 8, since I like @NonNull annotations and the Java 7 compatibility is really troublesome.) However I am keen that my project follows the Eclipse consensus, which does not seem to exist. My Hudson builds now fail so I need to know where the new consensus is. Regards Ed Willink On 04/03/2015 16:32, Konstantin Komissarchik wrote: What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the “no further public updates” phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _cannot_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin From: cross-project-issues-dev-boun...@eclipse.orgmailto:cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Ed Willink Sent: Wednesday, March 04, 2015 6:57 AM To: cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From:Ed Willink e...@willink.me.ukmailto:e...@willink.me.uk To:Cross project issues cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org Date:04.03.2015 15:27 Subject:[cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.orgmailto:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.orgmailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi Doug Indeed, But As stated above, /we expect that Eclipse works fine on other current Java VM and OS versions but we cannot flag these as reference platforms without significant community support for testing them./ This is a statement of tested support. The change to jdt.core breaks Java 6 support. i.e. it guarantees non-functionality on Java 6. Regards Ed Willink On 04/03/2015 16:59, Doug Schaefer wrote: Our consensus has always been to not have a consensus. Each project moved to where they needed to be when they needed to be. Obviously the decisions of other projects affect yours, particularly the platform. And for that, I go by their project plan which has no mention of JRE 6 for Mars. https://www.eclipse.org/projects/project-plan.php?planurl=/eclipse/development/plans/eclipse_project_plan_4_5.xml Doug. From: Ed Willink e...@willink.me.uk mailto:e...@willink.me.uk Reply-To: Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Date: Wednesday, March 4, 2015 at 11:46 AM To: cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi (I would love it if Mars required Java 8, since I like @NonNull annotations and the Java 7 compatibility is really troublesome.) However I am keen that my project follows the Eclipse consensus, which does not seem to exist. My Hudson builds now fail so I need to know where the new consensus is. Regards Ed Willink On 04/03/2015 16:32, Konstantin Komissarchik wrote: What is the rationale for wanting to keep BREE levels as low as possible? Even Java 7 enters the “no further public updates” phase in April of this year. JRE 7 users in the normal update pipeline were upgraded to Java 8 in January. Are there really users out there who _/cannot/_ run a newer version of the JRE despite security and performance implications of running an old version? I am guessing that if Mars were to require Java 8, there would be some initial grumbling over having to upgrade, then everyone moves on in a better and more secure configuration. http://www.oracle.com/technetwork/java/javase/downloads/eol-135779.html Thanks, - Konstantin *From:*cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Ed Willink *Sent:* Wednesday, March 04, 2015 6:57 AM *To:* cross-project-issues-dev@eclipse.org *Subject:* Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk mailto:e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.org mailto:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
On 04/03/2015 12:18 PM, Ed Willink wrote: But As stated above, /we expect that Eclipse works fine on other current Java VM and OS versions/ But Java 6 is not a current version of Java. It was EOL'd in 2013. See http://www.oracle.com/technetwork/java/eol-135779.html -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 (mobile) EclipseCon 2015 http://www.eclipsecon.org/na2015 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hey! I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Cheers, -Martin Am 04.03.2015 um 20:34 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 12:18 PM, Ed Willink wrote: But As stated above, we expect that Eclipse works fine on other current Java VM and OS versions But Java 6 is not a current version of Java. It was EOL'd in 2013. See http://www.oracle.com/technetwork/java/eol-135779.html -- Mike Milinkovich mike.milinkov...@eclipse.org +1.613.220.3223 (mobile) 100x130.jpg ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. I guess we just need to come up with a common definition of what we mean by current version. ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Is this thread about what minimum BREE to use, or is it about announcing changes to this? I agree with most people here that Java 7 is a sensible minimum BREE for Mars, but I get the sense that this thread was more about how / where these changes are announced. Cheers, Ian On Wed, Mar 4, 2015 at 2:36 PM, Gunnar Wagenknecht gun...@wagenknecht.org wrote: Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. And we have a solution for this too -- LTS. If someone wants support for Eclipse for an older version of Java, then LTS would be the obvious recommendation. :) I guess we just need to come up with a common definition of what we mean by current version. I say: it should be every version receiving security updates public and free accessible for the community (committers, contributors and users). As of May 2015, Java 7 will fall out of that list. But that's just my two cents. -Gunnar ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi I think that this thread is about both. Nobody has advanced a strong argument for retaining Java 6 support, so we can move on without upsetting anybody. Doug: if you examine the tabulated per-plugin BREEs in the platform project plan you will see a clear indication that jdt.core is 1.6. (The only 1.7 is the filesystem.java7 bundle.) Therefore IMHO this change should have been announced: a) because it was a change to the platform project plan b) because it clearly has an impact on many other projects Regards Ed Willink On 05/03/2015 01:02, Ian Bull wrote: Is this thread about what minimum BREE to use, or is it about announcing changes to this? I agree with most people here that Java 7 is a sensible minimum BREE for Mars, but I get the sense that this thread was more about how / where these changes are announced. Cheers, Ian On Wed, Mar 4, 2015 at 2:36 PM, Gunnar Wagenknecht gun...@wagenknecht.org mailto:gun...@wagenknecht.org wrote: Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org mailto:mike.milinkov...@eclipse.org: On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. And we have a solution for this too -- LTS. If someone wants support for Eclipse for an older version of Java, then LTS would be the obvious recommendation. :) I guess we just need to come up with a common definition of what we mean by current version. I say: it should be every version receiving security updates public and free accessible for the community (committers, contributors and users). As of May 2015, Java 7 will fall out of that list. But that's just my two cents. -Gunnar ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- R. Ian Bull | EclipseSource Victoria | +1 250 477 7484 http://eclipsesource.com | http://twitter.com/eclipsesource ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9227 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
- Original Message - From: Gunnar Wagenknecht gun...@wagenknecht.org To: Mike Milinkovich mike.milinkov...@eclipse.org, Cross project issues cross-project-issues-dev@eclipse.org Sent: Thursday, March 5, 2015 12:36:30 AM Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE Am 04.03.2015 um 13:53 schrieb Mike Milinkovich mike.milinkov...@eclipse.org: On 04/03/2015 4:15 PM, Martin Lippert wrote: I am not sure whether this “end of public updates” date reflects what is going on inside organizations. Oracle still offers support for Java6 until Dec 2015, and extended support for Dec 2018. http://www.oracle.com/technetwork/java/eol-135779.html#java-commercial-offerings Sure. And I'm also sure if you pay Microsoft enough money you can get support for Windows XP as well. That doesn't make it current. And we have a solution for this too -- LTS. If someone wants support for Eclipse for an older version of Java, then LTS would be the obvious recommendation. :) I guess we just need to come up with a common definition of what we mean by current version. I say: it should be every version receiving security updates public and free accessible for the community (committers, contributors and users). That's the key here - if committers/contributors can't get free access to given version instantly claiming it supported is not helping anybody as it will be untested and if an issue arise there will be no one looking at it (even to commit a patch if you can't test it and it's not obvious). Alexander Kurtakov Red Hat Eclipse team As of May 2015, Java 7 will fall out of that list. But that's just my two cents. -Gunnar ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject:[cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by:cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Hi But this is important. When osgi.utils moved from Java 5 to Java 6 that made Eclipse almost unuseable as a Java 5 platform; not really a problem. Now jdt.core does nearly the same thing for Eclipse as a Java 6 platform. Are we ready to go that far? IMHO it certainly should be discussed and announced. Regards Ed Willink On 04/03/2015 14:42, Daniel Megert wrote: Hi Ed Yes, this was intended. We never announce BREE changes. Dani From: Ed Willink e...@willink.me.uk To: Cross project issues cross-project-issues-dev@eclipse.org Date: 04.03.2015 15:27 Subject: [cross-project-issues-dev] jdt.core move to Java 7 BREE Sent by: cross-project-issues-dev-boun...@eclipse.org Hi Is the recent change in BREE for org.eclipse.jdt.core from Java 6 to Java 7 intended? Was it announced? Regards Ed Willink ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev No virus found in this message. Checked by AVG - www.avg.com http://www.avg.com Version: 2015.0.5751 / Virus Database: 4299/9224 - Release Date: 03/04/15 ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
