Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344734 - [1.7] Create branch BETA_JAVA7 of org.eclipse.osgi
Summary: [1.7] Create branch BETA_JAVA7 of org.eclipse.osgi
Status: RESOLVED FIXED
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: 3.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 342322
Blocks:
  Show dependency tree
 
Reported: 2011-05-04 13:10 EDT by Markus Keller CLA
Modified: 2011-05-05 08:57 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-05-04 13:10:26 EDT
Follow-up to bug 342322.

With org.eclipse.osgi from HEAD, the compiler compliance for the 1.7 EE is set to 1.6. This is wrong for users of the BETA_JAVA7 branch from jdt.core and jdt.ui.

Could you please create a BETA_JAVA7 branch from HEAD and revert the patch from bug 342322 comment 1 there?
Comment 1 Thomas Watson CLA 2011-05-04 14:11:31 EDT
Would it be better to branch for 3.7 and start doing the next release work in HEAD?
Comment 2 Olivier Thomann CLA 2011-05-04 17:49:38 EDT
We would like to have all bundles involved in the Java 7 effort ready soon so that we can start working on a p2 repository to let users try our current Java 7 support.
Comment 3 Dani Megert CLA 2011-05-05 02:54:54 EDT
(In reply to comment #2)
> We would like to have all bundles involved in the Java 7 effort ready soon so
> that we can start working on a p2 repository to let users try our current Java
> 7 support.

+1. We don't want to wait until HEAD is frozen and tagged with 'R3_7'. We already work in BETA_JAVA7 branches on other JDT projects.
Comment 4 Thomas Watson CLA 2011-05-05 08:57:23 EDT
Done, the 1.7 profile has the correct compiler settings for Java 7 in the branch.  I created bug344833 to remind me to do the same in the 3.7_maintenance stream once it is created (I assume we will be doing this in 3.7.1 also).