Community
Participate
Working Groups
Fragment name is org.eclipse.pde.api.tools.ee.javase17 This change needs to be made in both the 3.7.x and 3.8 stream builds.
Created attachment 200812 [details] patch for 3.8 stream
Created attachment 200813 [details] patch for 3.7.x stream
Kim, we ship the Java 7 support with M1, hence this should go into M1.
Yes Dani, I've released it and am running a test build :-)
> Yes Dani, I've released it and am running a test build :-) Awesome!
Verified in test build.
(In reply to comment #6) > Verified in test build. How does it come to the update site? Currently it is still not available at: http://download.eclipse.org/eclipse/updates/3.7
.
Dani, this update site is for the 3.7 release only. The update sites for 3.7.x M builds and 3.8 I-builds are listed here http://wiki.eclipse.org/Eclipse_Project_Update_Sites
I use what's installed in my download ;-)
Could me copy the fragment over to http://download.eclipse.org/eclipse/updates/3.7?
I verified that the 1.7 EE is available at "Eclipse Project Test Site" - http://download.eclipse.org/eclipse/updates/3.8-I-builds and works as expected.
With respect to comment 11, the release repo is immutable. We are not yet at the state where we can release 3.7.1. So what you're asking for is that we provide a child repo within the composite repository that provides a new pde api tools feature that provides the java 7 fragment? But not the other bundles and features in the 3.7.x stream that provide actual Java 7 support? This seems like a unusual request.
(In reply to comment #13) > With respect to comment 11, the release repo is immutable. We are not yet at > the state where we can release 3.7.1. So what you're asking for is that we > provide a child repo within the composite repository that provides a new pde > api tools feature that provides the java 7 fragment? But not the other bundles > and features in the 3.7.x stream that provide actual Java 7 support? This > seems like a unusual request. No, I'm asking the the M- and I-builds come configured with the correct update sites.
Our I and M builds don't come configured with p2 repo urls for development or non-release builds because of a clause in the Eclipse development process. http://www.eclipse.org/projects/dev_process/development_process_2011.php#6_4_Releases "(Exception 1: nightly and integration builds) During the process of developing software and preparing a Release, various nightly and integration builds are made available to the developer community for testing purposes. Do not include any links on the project website, blogs, wikis, etc. that might encourage non-early-adopters to download and use nightly builds, release candidates, or any other similar package (links aimed at early-adopters and the project's developers are both permitted and encouraged). The only people who are supposed to know about such packages are the people following the developer mailing list and thus are aware of the limitations of such builds." We had a bug a few years ago from an consumer in the community requesting that we change this but the PMC decided not to because of the caveats in the Eclipse development process. (I couldn't find the bug :-) You can just add the development stream p2 repo urls to your install, that's what I do.
(In reply to comment #15) Point taken ;-). I've added a link http://wiki.eclipse.org/Eclipse_Project_Update_Sites in our Java 7 What's New.
