Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread John Arthorne 
The fact that the Eclipse SDK as a whole will require Java 8 doesn't imply that any particular bundle should require Java 8. Since the change requiring Java 8 was cosmetic and there is a significant impact caused by the change, I think it is fair to ask the question and to consider the request. I have entered this bug for further discussion, so please chime in there if you have an opinion:https://bugs.eclipse.org/bugs/show_bug.cgi?id=483803One question for you Ralf, is whether this is the only bundle RAP requires that is blocking you in this way? I thought there were a number of other platform bundles already requiring Java 8 as well.John-cross-project-issues-dev-boun...@eclipse.org wrote: -To: Cross project issues From: Lars Vogel Sent by: cross-project-issues-dev-boun...@eclipse.orgDate: 12/07/2015 04:50AMSubject: Re: [cross-project-issues-dev] core.jobs dependency on Java 8Hi Ralf,Dani announced a while ago that Eclipse Neon will drop support forJava 7. See: https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12177.htmlBest regards, LarsOn Mon, Dec 7, 2015 at 10:41 AM, Ralf Sternberg wrote:> Hi,>> while we all want to use the new features in Java 8, some users of the> RAP project still can't switch to Java 8 because they have to deploy> on application servers that run on a (bundled) non-Java-8 VM. For> example, looking at the IBM WebSphere JDK support list [1], it seems> that for the server side, it's still a bit too early to require Java> 8.>> Since one of the bundles RAP depends on (core.jobs) has recently been> updated to Java 8, we find ourselves faced with the choice of either> locking out those users or shipping RAP 3.1 with an older version of> the platform. The latter would probably mean to abstain from the Neon> simultaneous release.>> I wonder if there is a general consensus that the Eclipse platform> (not the IDE) does not support Java 7 anymore. If this is the case, we> have to live with it, however, I'd appreciate to keep at least the> core Java-7-compatible for one more year. Looking at the respective> change in core.jobs [2], it looks like a refactoring, not an API> change that would require Java 8. Also on the Neon release plan [3],> it's still marked as 1.7. Is there a chance to revert this change or> are more of those going to come?>> Regards,> Ralf>> [1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002> [2] http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29> [3] https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix>> --> Ralf Sternberg> Project Lead, Remote Application Platform (RAP)> EclipseSource>> Tel: +49 721 66 47 33-0>> Innoopract Informationssysteme GmbH> Lammstraße 21, 76133 Karlsruhe, Germany> General Manager: Jochen Krause> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883> ___> cross-project-issues-dev mailing list> cross-project-issues-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev-- Eclipse Platform UI and e4 project co-leadCEO vogella GmbHHaindaalwisch 17a, 22395 HamburgAmtsgericht Hamburg: HRB 127058Geschäftsführer: Lars Vogel, Jennifer Nerlich de VogelUSt-IdNr.: DE284122352Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: http://www.vogella.com___cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orgTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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

Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Ivan Furnadjiev 

Hi John,
today I found that another set of bundles that RAP uses from platform 
depends now on Java 8:

org.eclipse.core.databinding
org.eclipse.core.databinding.property
org.eclipse.core.databinding.observable
Regards,
Ivan

On 12/7/2015 16:40, John Arthorne wrote:
The fact that the Eclipse SDK as a whole will require Java 8 doesn't 
imply that any particular bundle should require Java 8. Since the 
change requiring Java 8 was cosmetic and there is a significant impact 
caused by the change, I think it is fair to ask the question and to 
consider the request. I have entered this bug for further discussion, 
so please chime in there if you have an opinion:


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

One question for you Ralf, is whether this is the only bundle RAP 
requires that is blocking you in this way? I thought there were a 
number of other platform bundles already requiring Java 8 as well.


John


-cross-project-issues-dev-boun...@eclipse.org 
 wrote: -
To: Cross project issues >

From: Lars Vogel
Sent by: cross-project-issues-dev-boun...@eclipse.org 


Date: 12/07/2015 04:50AM
Subject: Re: [cross-project-issues-dev] core.jobs dependency on Java 8

Hi Ralf,

Dani announced a while ago that Eclipse Neon will drop support for
Java 7. See: 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12177.html


Best regards, Lars

On Mon, Dec 7, 2015 at 10:41 AM, Ralf Sternberg
> 
wrote:

> Hi,
>
> while we all want to use the new features in Java 8, some users of the
> RAP project still can't switch to Java 8 because they have to deploy
> on application servers that run on a (bundled) non-Java-8 VM. For
> example, looking at the IBM WebSphere JDK support list [1], it seems
> that for the server side, it's still a bit too early to require Java
> 8.
>
> Since one of the bundles RAP depends on (core.jobs) has recently been
> updated to Java 8, we find ourselves faced with the choice of either
> locking out those users or shipping RAP 3.1 with an older version of
> the platform. The latter would probably mean to abstain from the Neon
> simultaneous release.
>
> I wonder if there is a general consensus that the Eclipse platform
> (not the IDE) does not support Java 7 anymore. If this is the case, we
> have to live with it, however, I'd appreciate to keep at least the
> core Java-7-compatible for one more year. Looking at the respective
> change in core.jobs [2], it looks like a refactoring, not an API
> change that would require Java 8. Also on the Neon release plan [3],
> it's still marked as 1.7. Is there a chance to revert this change or
> are more of those going to come?
>
> Regards,
> Ralf
>
> [1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002
> [2] 
http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29
> [3] 
https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix

>
> --
> Ralf Sternberg
> Project Lead, Remote Application Platform (RAP)
> EclipseSource
>
> Tel: +49 721 66 47 33-0
>
> Innoopract Informationssysteme GmbH
> Lammstraße 21, 76133 Karlsruhe, Germany
> General Manager: Jochen Krause
> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org 

> To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vo...@vogella.com 
, Web: http://www.vogella.com

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org 

To change your delivery options, retrieve your password, or 
unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



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


___
cross-project-issues-dev mailing list

Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Konstantin Komissarchik 
> I would imagine by the time Neon is released in June and used to build RAP
> applications most all the major app servers should support Java 8.

Indeed. Java 8 is already supported by GlassFish (since version 4) and WebLogic 
Server (since version 12.1.3).

Thanks,

- Konstantin



From: Thomas Watson
Sent: Monday, December 7, 2015 9:13 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] core.jobs dependency on Java 8


One thing to note is that Java 8 is already supported for WebShere Application 
Server Liberty.  Also, the statement of general direction from IBM is that IBM 
intends to support Java 8 for WebSphere Application Server - Classic [1]

I would imagine by the time Neon is released in June and used to build RAP 
applications most all the major app servers should support Java 8.

Tom

[1] 
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN=CA=897/ENUS215-417=USN#sodx




From:        Ivan Furnadjiev 
To:        cross-project-issues-dev@eclipse.org
Date:        12/07/2015 09:32 AM
Subject:        Re: [cross-project-issues-dev] core.jobs dependency on Java 8
Sent by:        cross-project-issues-dev-boun...@eclipse.org




Hi John,
today I found that another set of bundles that RAP uses from platform depends 
now on Java 8:
org.eclipse.core.databinding
org.eclipse.core.databinding.property
org.eclipse.core.databinding.observable
Regards,
Ivan

On 12/7/2015 16:40, John Arthorne wrote:
The fact that the Eclipse SDK as a whole will require Java 8 doesn't imply that 
any particular bundle should require Java 8. Since the change requiring Java 8 
was cosmetic and there is a significant impact caused by the change, I think it 
is fair to ask the question and to consider the request. I have entered this 
bug for further discussion, so please chime in there if you have an opinion: 

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

One question for you Ralf, is whether this is the only bundle RAP requires that 
is blocking you in this way? I thought there were a number of other platform 
bundles already requiring Java 8 as well.

John


-cross-project-issues-dev-bounces@eclipse.orgwrote: - 
To: Cross project issues 
From: Lars Vogel 
Sent by: cross-project-issues-dev-boun...@eclipse.org
Date: 12/07/2015 04:50AM
Subject: Re: [cross-project-issues-dev] core.jobs dependency on Java 8

Hi Ralf,

Dani announced a while ago that Eclipse Neon will drop support for
Java 7. See: 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12177.html

Best regards, Lars

On Mon, Dec 7, 2015 at 10:41 AM, Ralf Sternberg
 wrote:
> Hi,
>
> while we all want to use the new features in Java 8, some users of the
> RAP project still can't switch to Java 8 because they have to deploy
> on application servers that run on a (bundled) non-Java-8 VM. For
> example, looking at the IBM WebSphere JDK support list [1], it seems
> that for the server side, it's still a bit too early to require Java
> 8.
>
> Since one of the bundles RAP depends on (core.jobs) has recently been
> updated to Java 8, we find ourselves faced with the choice of either
> locking out those users or shipping RAP 3.1 with an older version of
> the platform. The latter would probably mean to abstain from the Neon
> simultaneous release.
>
> I wonder if there is a general consensus that the Eclipse platform
> (not the IDE) does not support Java 7 anymore. If this is the case, we
> have to live with it, however, I'd appreciate to keep at least the
> core Java-7-compatible for one more year. Looking at the respective
> change in core.jobs [2], it looks like a refactoring, not an API
> change that would require Java 8. Also on the Neon release plan [3],
> it's still marked as 1.7. Is there a chance to revert this change or
> are more of those going to come?
>
> Regards,
> Ralf
>
> [1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002
> [2] 
> http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29
> [3] 
> https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix
>
> --
> Ralf Sternberg
> Project Lead, Remote Application Platform (RAP)
> EclipseSource
>
> Tel: +49 721 66 47 33-0
>
> Innoopract Informationssysteme GmbH
> Lammstraße 21, 76133 Karlsruhe, Germany
> General Manager: Jochen Krause
> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395

Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Thomas Watson 
One thing to note is that Java 8 is already supported for WebShere 
Application Server Liberty.  Also, the statement of general direction from 
IBM is that IBM intends to support Java 8 for WebSphere Application Server 
- Classic [1]

I would imagine by the time Neon is released in June and used to build RAP 
applications most all the major app servers should support Java 8.

Tom

[1] 
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN=CA=897/ENUS215-417=USN#sodx





From:   Ivan Furnadjiev 
To: cross-project-issues-dev@eclipse.org
Date:   12/07/2015 09:32 AM
Subject:Re: [cross-project-issues-dev] core.jobs dependency on 
Java 8
Sent by:cross-project-issues-dev-boun...@eclipse.org



Hi John,
today I found that another set of bundles that RAP uses from platform 
depends now on Java 8:
org.eclipse.core.databinding
org.eclipse.core.databinding.property
org.eclipse.core.databinding.observable
Regards,
Ivan

On 12/7/2015 16:40, John Arthorne wrote:
The fact that the Eclipse SDK as a whole will require Java 8 doesn't imply 
that any particular bundle should require Java 8. Since the change 
requiring Java 8 was cosmetic and there is a significant impact caused by 
the change, I think it is fair to ask the question and to consider the 
request. I have entered this bug for further discussion, so please chime 
in there if you have an opinion: 

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

One question for you Ralf, is whether this is the only bundle RAP requires 
that is blocking you in this way? I thought there were a number of other 
platform bundles already requiring Java 8 as well.

John


-cross-project-issues-dev-boun...@eclipse.org wrote: - 
To: Cross project issues 
From: Lars Vogel 
Sent by: cross-project-issues-dev-boun...@eclipse.org
Date: 12/07/2015 04:50AM
Subject: Re: [cross-project-issues-dev] core.jobs dependency on Java 8

Hi Ralf,

Dani announced a while ago that Eclipse Neon will drop support for
Java 7. See: 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12177.html


Best regards, Lars

On Mon, Dec 7, 2015 at 10:41 AM, Ralf Sternberg
 wrote:
> Hi,
>
> while we all want to use the new features in Java 8, some users of the
> RAP project still can't switch to Java 8 because they have to deploy
> on application servers that run on a (bundled) non-Java-8 VM. For
> example, looking at the IBM WebSphere JDK support list [1], it seems
> that for the server side, it's still a bit too early to require Java
> 8.
>
> Since one of the bundles RAP depends on (core.jobs) has recently been
> updated to Java 8, we find ourselves faced with the choice of either
> locking out those users or shipping RAP 3.1 with an older version of
> the platform. The latter would probably mean to abstain from the Neon
> simultaneous release.
>
> I wonder if there is a general consensus that the Eclipse platform
> (not the IDE) does not support Java 7 anymore. If this is the case, we
> have to live with it, however, I'd appreciate to keep at least the
> core Java-7-compatible for one more year. Looking at the respective
> change in core.jobs [2], it looks like a refactoring, not an API
> change that would require Java 8. Also on the Neon release plan [3],
> it's still marked as 1.7. Is there a chance to revert this change or
> are more of those going to come?
>
> Regards,
> Ralf
>
> [1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002
> [2] 
http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29

> [3] 
https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix

>
> --
> Ralf Sternberg
> Project Lead, Remote Application Platform (RAP)
> EclipseSource
>
> Tel: +49 721 66 47 33-0
>
> Innoopract Informationssysteme GmbH
> Lammstraße 21, 76133 Karlsruhe, Germany
> General Manager: Jochen Krause
> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: 
http://www.vogella.com
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit

Re: [cross-project-issues-dev] CBI Maven plugins 1.1.3-SNAPSHOT

2015-12-07 Thread Kaloyan Raev 
Hi Mikael,

I am very excited about the digestAlgorithm option because I hope it can be
the solution for Eclipse Bug 378155 [1]. The issue is that the plugins
which are signed with the eclipse-jarsigner-plugin cannot be installed on
Eclipse Indigo and earlier. I tried to use the TestServer to see if I can
sign the plugins with SHA-1 so they can be successfully installed on
Eclipse Indigo, but I've hit some roadblocks.

1. The full qualified class name must be provided in the command,
i.e. org.eclipse.cbi.webservice.signing.jar.TestServer. This was easy to
resolve.

2. I get a NullPointerException when starting the Test Server. I looked at
the source code to find that this is due to missing HTTP_PROXY environment
variable on my system. My system has a direct Internet connection, so it
does not make sense to define such variables. I had to checkout the code,
comment some lines and run it from Eclipse to resolve this issue.

3. The signing with the Test Server is very slow. It takes around a minute
to sign a single jar file. My CPU is not utilized at all. I have no
solution for this.

4. I tried using the SHA_1 digest algorithm, but the result is not the same
as the JAR being signed with Java 6. I have "SHA-1-Digest" headers in he
MANIFEST.MF file instead of "SHA1-Digest". Note the extra dash. So, the
installation of these plugins on Eclipse Indigo is still not successful. I
did not find a valid configuration for the digestAlgorithm option to get
the correct "SHA1-Digest" header. I tried with SHA1, but I got an error
that it is not a valid value.

I hope you can give me some hints how I can use version 1.1.3-SNAPSHOT to
sign the plugins in a way that they can be installed successfully on
Eclipse Indigo.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=378155

Thanks,
Kaloyan

On Tue, Oct 20, 2015 at 1:36 PM, Mikael Barbero  wrote:

> Hi,
>
> I just released version 1.1.3-SNAPSHOT of CBI maven plugins. Please give
> it a try. You should only need to change the version from whatever you use
> to 1.1.3-SNAPSHOT. Here is the list of changes:
>
> * A lot of things have changed under the hood to provide better
> reliability and the plugins are now extensively tested.
>
> * A new plugin has appeared (
> https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-dmg-packager/package-dmg-mojo.html)
> thanks to Pascal Rapicault: the dmg packager. It gives you the possibility
> to package an OS X application as a DMG (Apple's .msi equivalent). Please
> note that this plugin is still in beta-stage, but feedback is more than
> welcome!
>
> * Two new options has been added to the jarsigner plugin (to fix
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=473402):
> - digestAlgorithm (
> https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#digestAlgorithm
> )
> - resignStrategy (
> https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-jarsigner-plugin/sign-mojo.html#resigningStrategy
> )
>
> * Non qualified properties (e.g. -DcontinueOnFail) have been deprecated in
> favor of qualified properties (-D cbi.jarsigner.continueOnFail) to avoid
> collision with other plugins. Non qualified properties are still supported,
> but they are implemented by parameter starting with "deprecated". It should
> not changed anything for people who don't use user properties (i.e. '-D' on
> the maven command line). If you do, you will see a deprecation warning.
>
> * Staging documentation is available here
> https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/. You will see that
> documentation for a low-level plugin is now available (
> https://www.eclipse.org/cbi/sitedocs/1.1.3-SNAPSHOT/eclipse-cbi-plugin/plugin-info.html
> )
>
> * A standalone test server is available to help people debug jar signing
> locally, without the need to run builds on the Eclipse servers. Just
> download
> https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22.jar
>  and
> https://repo.eclipse.org/content/repositories/cbi/org/eclipse/cbi/jar-signing-service/1.0.0-SNAPSHOT/jar-signing-service-1.0.0-20151020.095931-22-tests.jar
>  (or
> more recent) and run the following command
>
> java -cp
> /path/where/you/download/the/jars/jar-signing-service-1.0.0-20151020.095931-22.jar:/path/where/you/download/the/jars/jar-signing-service-1.0.0-20151020.095931-22-tests.jar:
> TestServer
>
> It will print an URL (like http://localhost:3138/jarsigner) that you can
> add to your maven build (-Dcbi.jarsigner.signerUrl=
> http://localhost:3138/jarsigner) and it will sign your jars locally with
> a dummy certificate. You can pass --help to see the options you can give to
> the TestServer
>
> Thanks.
> Mikael
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe
> from this list,

Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Lars Vogel 
Hi Ralf,

Dani announced a while ago that Eclipse Neon will drop support for
Java 7. See: 
https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg12177.html

Best regards, Lars

On Mon, Dec 7, 2015 at 10:41 AM, Ralf Sternberg
 wrote:
> Hi,
>
> while we all want to use the new features in Java 8, some users of the
> RAP project still can't switch to Java 8 because they have to deploy
> on application servers that run on a (bundled) non-Java-8 VM. For
> example, looking at the IBM WebSphere JDK support list [1], it seems
> that for the server side, it's still a bit too early to require Java
> 8.
>
> Since one of the bundles RAP depends on (core.jobs) has recently been
> updated to Java 8, we find ourselves faced with the choice of either
> locking out those users or shipping RAP 3.1 with an older version of
> the platform. The latter would probably mean to abstain from the Neon
> simultaneous release.
>
> I wonder if there is a general consensus that the Eclipse platform
> (not the IDE) does not support Java 7 anymore. If this is the case, we
> have to live with it, however, I'd appreciate to keep at least the
> core Java-7-compatible for one more year. Looking at the respective
> change in core.jobs [2], it looks like a refactoring, not an API
> change that would require Java 8. Also on the Neon release plan [3],
> it's still marked as 1.7. Is there a chance to revert this change or
> are more of those going to come?
>
> Regards,
> Ralf
>
> [1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002
> [2] 
> http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29
> [3] 
> https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix
>
> --
> Ralf Sternberg
> Project Lead, Remote Application Platform (RAP)
> EclipseSource
>
> Tel: +49 721 66 47 33-0
>
> Innoopract Informationssysteme GmbH
> Lammstraße 21, 76133 Karlsruhe, Germany
> General Manager: Jochen Krause
> Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vo...@vogella.com, Web: http://www.vogella.com
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Ralf Sternberg 
Hi,

while we all want to use the new features in Java 8, some users of the
RAP project still can't switch to Java 8 because they have to deploy
on application servers that run on a (bundled) non-Java-8 VM. For
example, looking at the IBM WebSphere JDK support list [1], it seems
that for the server side, it's still a bit too early to require Java
8.

Since one of the bundles RAP depends on (core.jobs) has recently been
updated to Java 8, we find ourselves faced with the choice of either
locking out those users or shipping RAP 3.1 with an older version of
the platform. The latter would probably mean to abstain from the Neon
simultaneous release.

I wonder if there is a general consensus that the Eclipse platform
(not the IDE) does not support Java 7 anymore. If this is the case, we
have to live with it, however, I'd appreciate to keep at least the
core Java-7-compatible for one more year. Looking at the respective
change in core.jobs [2], it looks like a refactoring, not an API
change that would require Java 8. Also on the Neon release plan [3],
it's still marked as 1.7. Is there a chance to revert this change or
are more of those going to come?

Regards,
Ralf

[1] http://www-01.ibm.com/support/docview.wss?rs=180=swg27005002
[2] 
http://git.eclipse.org/c/platform/eclipse.platform.runtime.git/commit/bundles/org.eclipse.core.jobs?id=e0c1dc5111c5200d39f4611082b34110d735ac29
[3] 
https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_6.xml#appendix

--
Ralf Sternberg
Project Lead, Remote Application Platform (RAP)
EclipseSource

Tel: +49 721 66 47 33-0

Innoopract Informationssysteme GmbH
Lammstraße 21, 76133 Karlsruhe, Germany
General Manager: Jochen Krause
Registered Office: Karlsruhe, Commercial Register Mannheim HRB 107883
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] core.jobs dependency on Java 8

2015-12-07 Thread Ralf Sternberg 
Hi John,

thanks for your support.

> One question for you Ralf, is whether this is the only bundle RAP requires
> that is blocking you in this way? I thought there were a number of other
> platform bundles already requiring Java 8 as well.

Unfortunately, as Ivan reported already, there are three more
eclipse.core.databinding bundles now requiring Java 8 that I was not
aware of. All other dependencies of RAP (equinox, eclipse.core,
javax.servlet, javax.xml, icu) are still on <= 1.7.

As Lars pointed out in bug 483803, the planned support for the new
Date and Time API would require Java 8, so the core.databinding
bundles should remain on Java 8. I'd think that the databinding
bundles are less critical for us as databinding is an optional feature
and the bundles could probably easily be replaced by their Mars
versions in a Java 7 deployment.

Also thanks to Thomas and Konstantin for the pointers to Application
Servers and Java 8. We'll discuss again if moving to Java 8 could
already be an option for RAP 3.1.

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