Community
Participate
Working Groups
Some consumers of org.eclipse.core.jobs are affected by the move to require Java 8. In particular RAP will no longer be able to participate in the Neon simultaneous release due to this limitation: http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12737.html Since the change requiring Java 8 was cosmetic, we should consider reverting that to help out our consumer community. This is the commit that would need reverting to fix it: http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=e0c1dc5111c5200d39f4611082b34110d735ac29
One 'advantage' of the move to Java 8 is to remove ambiguity in the unfortunately incompatible Java 7/8 jdt.annotation support. I find it convenient that I no longer need to make any pretence at supporting the Java 7 source available in Luna/Mars for Eclipse OCL. Java 7 is after all EOL, so we should move on. If the platform supports Java 7 again, maybe I have to too.
We moved lots of platform plug-ins already to Java 8, I doubt that moving one plug-ins back will help RAP.
(In reply to Ed Willink from comment #1) > If the platform supports Java 7 again, maybe I have to too. It all depends on what your consumers want to do with your bundles. Just because one bundle in a release moves up to Java 8 does not mean all bundles in the release have to move up. Many bundles can be consumed independent of other bundles in a release. In my opinion low level components, such as jobs, should not be moved up to the very latest Java without considering how the community consumes the individual bundles.
I've checked again, besides org.eclipse.core.jobs, these core.databinding bundles have also been updated to Java 8 recently[1]: org.eclipse.core.databinding org.eclipse.core.databinding.observable org.eclipse.core.databinding.property While this change did not affect the API, there is one change on top of it that requires Java 8 [2]. [1] http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/bundles/org.eclipse.core.databinding?id=5e2ca9d1501a11fa56ef0de27bfc3d9884216a51 [2] http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/bundles/org.eclipse.core.databinding?id=a2a9931aba4ab34dcaa72612d8343824a62cf726
<stuff deleted> >Since the change requiring Java 8 was cosmetic, we should consider reverting >that to help out our consumer community. This is the commit that would need >reverting to fix it: > >http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?>id=e0c1dc5111c5200d39f4611082b34110d735ac29 ECF depends upon the jobs API for async remote services (server/peers/clients) as well as some of it's Eclipse-based tooling. We would like to continue supporting Java 7 for remote services for at least one more release cycle, but the good news is that we certainly could do this by not consuming the Neon version of jobs (i.e. using and distributing the Mars version of jobs) as Thomas suggests in comment 3. Though this can/might make things overly complicated for us an our consumers once Neon is released. However, since these changes do seem to be only cosmetic, we would be +1 to having jobs remain with Java7 for Neon.
Sergey / Stefan, anything you need from Java 8 for jobs or can we revert it to Java 7?
(In reply to Ralf Sternberg from comment #4) > org.eclipse.core.databinding > org.eclipse.core.databinding.observable > org.eclipse.core.databinding.property For databinding we are planning to support the new Java 8 Date and Time API, so we should not revert that to Java 7.
(In reply to Lars Vogel from comment #6) I do not object to reverting jobs to Java 7 for Neon.
(In reply to Sergey Prigogin from comment #8) > (In reply to Lars Vogel from comment #6) > > I do not object to reverting jobs to Java 7 for Neon. Thanks Sergey. If this helps RAP and ECF, I suggest to revert jobs to Java 7 in M5.
> For databinding we are planning to support the new Java 8 Date and Time API, > so we should not revert that to Java 7. Agreed, databinding should stay on Java 8... but I think this bug is only asking about jobs.
In our PMC call today [1] we decided to move back to JavaSE-1.7. [1] https://wiki.eclipse.org/Eclipse/PMC#Meeting_Minutes
Update from RAP: In today's meeting we agreed to - keep RAP 3.1 in the Neon simultaneous release despite the core.databinding dependencies on Java 8 - keep the RAP 3.1 bundles Java 7 compatible - provide an alternative target platform based on Eclipse Mars for Java 7 users. With this policy, the core.jobs BREE would not be an issue for RAP anymore. However, for users that depend on Java 7 but don't require databinding, having core.jobs on 1.7 would still allow them to use the Neon version.
Ralf, thanks for the update. I suggest that we still move back to Java 7 for jobs to help ECF.
(In reply to Lars Vogel from comment #13) > Ralf, thanks for the update. I suggest that we still move back to Java 7 for > jobs to help ECF. Yes, see comment 11.
New Gerrit change created: https://git.eclipse.org/r/65088
Gerrit change https://git.eclipse.org/r/65088 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/?id=c50cee940e71a1489950a579032a4effc66648a7
Jobs backported to Java 7 for M5.
