[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Meeting this Wednesday

Why can't we currently test running on Java 9? I've been doing it for months.

Wayne


On 01/03/17 08:56 AM, Ed Merks wrote:

Thomas,

Thanks for being clear on that issue.  Support for compiling and developing Java 9 falls primarily on JDT (I assume/guess).  But support for running the IDE itself on Java 9 and making sure that works correctly is a burden that falls on us all.  Given we can't currently even test that, it seems to me it's not a great idea plan that way.   Like you, I don't feel comfortable planning an Oxygen release date around a Java release date.  More flexible and less risky in my opinion would be an Oxygen.0a  update that could respin primarily any JDT updates that are needed and would not be so much focused on the statement that the IDE itself will run on top of Java 9.  I.e., more along the line of what Nick is suggesting...


On 01.03.2017 14:48, Thomas Watson wrote:
Bug 493761 needs to be fixed for Oxygen.0.  The issue of launching the Eclipse platform on Java 9 is different than having the support for compiling and developing Java 9 classes.
 
I worry about delaying Oxygen.0 to align with Java 9 release because I can easily see the Java 9 release getting delayed again.  I would not want to hold up Oxygen.0 for that.

Tom
 
 
 
----- Original message -----
From: Ed Merks <ed.merks@xxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
To: eclipse.org-planning-council@xxxxxxxxxxx
Cc:
Subject: Re: [eclipse.org-planning-council] Meeting this Wednesday
Date: Wed, Mar 1, 2017 3:36 AM
 

I'm not sure the current of being able to run with Java 9, let alone supporting its features well in JDT:

 

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761

 

I assume this must be fixed in a general way that works regardless of whether Java 9 is actually used or not and regardless of the JVM implementation provider.  Is it hopeful that this will be addressed in time that we may all test the state of Java 9? 

 

Does it really make sense to plan the whole release schedule around this assumption?  And as Marc suggests, is planning a release during the high vacation season a good plan?

 

 
On 28.02.2017 18:51, Marc Khouzam wrote:

+1

Considering the dates are so close between Oxygen.0 and Java 9,

I think having an extra release is more hassle for adopters than it is worth.

So waiting for Java 9 is a good plan for Oxygen.0.

 

One drawback I see is that more people will be on vacation at that time,

but with proper planning, it should not be a problem.

 

Marc

 

From: eclipse.org-planning-council-bounces@xxxxxxxxxxx <eclipse.org-planning-council-bounces@xxxxxxxxxxx> on behalf of Martin Lippert <mlippert@xxxxxxxxx>
Sent: February 28, 2017 3:47
To: Eclipse Planning Council private list
Subject: Re: [eclipse.org-planning-council] Meeting this Wednesday
 
+1 for moving the Oxygen.0 release to the JDK9 release date.
Would make things for adopters of that release easier, too.

Cheers,
-Martin



> Note that I've added a biggie to the list: with all the talk about having an extra release to coincide with the Java 9 release, we've neglected to ask why we need a release in both June and July. The Java 9 release date (which by all accounts is pretty stable) is about a month after our planned Oxygen date. Is there any reason why we shouldn't just move the Oxygen.0 date (other than "we've always done it that way") ?
>
> Feel free to answer here. It would be great if you can come to the meeting armed with an answer to that question.
>
> See you on Wednesday.
>
> For all phone lines: Participant conference extension: 710 then enter pin 35498
>
> North America (toll free) 1-866-569-4992
> Germany (local call anywhere in Germany) +49-692-2224-6059
> France (local call anywhere in France) +33-17-070-8535
> UK (toll free) 0800-033-7806
> Switzerland (local call anywhere in Switzerland) +41-44-580-2115
> SIP clients: call 710@xxxxxxxxxxxxxxxxxxxx, then enter pin 35498.
> Wayne
> [1] https://wiki.eclipse.org/Planning_Council/February_01_2017
>
> [2] https://wiki.eclipse.org/Planning_Council/March_01_2017
>
> --
> Wayne Beaton
> @waynebeaton
> The Eclipse Foundation
> <ConvergeLogo_Transparent.png>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
dev.eclipse.org
Mailing list for private discussions amongst members of the Eclipse Planning Council. Using eclipse.org-planning-council To post a message to all the ...


>
> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
dev.eclipse.org
Mailing list for private discussions amongst members of the Eclipse Planning Council. Using eclipse.org-planning-council To post a message to all the ...



IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
 
 
 
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
 
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
 



_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.



_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
Eclipse
          Converge

PNG image