[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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

Inactive hide details for cross-project-issues-dev-request---03/05/2015 03:27:46 PM---Send cross-project-issues-dev mailing liscross-project-issues-dev-request---03/05/2015 03:27:46 PM---Send cross-project-issues-dev mailing list submissions to  cross-project-issues-dev@xxxxxxxxxxx

From: cross-project-issues-dev-request@xxxxxxxxxxx
To: cross-project-issues-dev@xxxxxxxxxxx
Date: 03/05/2015 03:27 PM
Subject: cross-project-issues-dev Digest, Vol 110, Issue 10
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx





Send cross-project-issues-dev mailing list submissions to
cross-project-issues-dev@xxxxxxxxxxx

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-request@xxxxxxxxxxx

You can reach the person managing the list at
cross-project-issues-dev-owner@xxxxxxxxxxx

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.merks@xxxxxxxxx>
To: cross-project-issues-dev@xxxxxxxxxxx
Subject: Re: [cross-project-issues-dev] Update site time outs
Message-ID: <54F80B95.7030305@xxxxxxxxx>
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@xxxxxxxxxxx
> 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 <akurtako@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Message-ID:
<686168366.23266320.1425542153656.JavaMail.zimbra@xxxxxxxxxx>
Content-Type: text/plain; charset=utf-8

----- Original Message -----
> From: "Gunnar Wagenknecht" <gunnar@xxxxxxxxxxxxxxx>
> To: "Mike Milinkovich" <mike.milinkovich@xxxxxxxxxxx>, "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
> 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.milinkovich@xxxxxxxxxxx>:
> >
> > 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@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


------------------------------

Message: 3
Date: Thu, 5 Mar 2015 02:59:50 -0500 (EST)
From: Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Message-ID:
<543338518.23268055.1425542390711.JavaMail.zimbra@xxxxxxxxxx>
Content-Type: text/plain; charset=utf-8

----- Original Message -----
> From: "Ed Willink" <ed@xxxxxxxxxxxxx>
> To: cross-project-issues-dev@xxxxxxxxxxx
> 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 < gunnar@xxxxxxxxxxxxxxx >
> wrote:
>
>
> > Am 04.03.2015 um 13:53 schrieb Mike Milinkovich <
> > mike.milinkovich@xxxxxxxxxxx >:
> >
> > 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@xxxxxxxxxxx
> 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@xxxxxxxxxxx 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@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


------------------------------

Message: 4
Date: Thu, 5 Mar 2015 10:56:55 +0100
From: Daniel Megert <daniel_megert@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] jdt.core move to Java 7 BREE
Message-ID:
<OFEF0CDAC6.274393D3-ONC1257DFF.0034078C-C1257DFF.0036A6A3@xxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

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 <ed@xxxxxxxxxxxxx>
To:     cross-project-issues-dev@xxxxxxxxxxx
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-bounces@xxxxxxxxxxx



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 <gunnar@xxxxxxxxxxxxxxx
> wrote:
> Am 04.03.2015 um 13:53 schrieb Mike Milinkovich <
mike.milinkovich@xxxxxxxxxxx>:
>
> 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@xxxxxxxxxxx
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@xxxxxxxxxxx
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@xxxxxxxxxxx
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/362db9f4/attachment.html>

------------------------------

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

End of cross-project-issues-dev Digest, Vol 110, Issue 10
*********************************************************


GIF image