Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » RAP 3.1 dependency on Java 1.8(Is RAP 3.1 now dependent on Java 1.8)
RAP 3.1 dependency on Java 1.8 [message #1709684] Wed, 30 September 2015 11:19 Go to next message
John Gymer is currently offline John GymerFriend
Messages: 279
Registered: November 2012
Location: UK
Senior Member
After updating to RAP 3.1 Nightly (29th/30th Sept 2015), it seems that some of the required dependencies have increased their minimum Java version to 1.8. Have I messed up my Target, or is this actually true?
I'm not sure we can enforce this requirement on our customers, so is it possible to revert other dependencies so that 1.7 is viable?

index.php/fa/23400/0/

Thanks, John


---
Just because you can doesn't mean you should
Re: RAP 3.1 dependency on Java 1.8 [message #1709698 is a reply to message #1709684] Wed, 30 September 2015 13:17 Go to previous messageGo to next message
Markus Knauer is currently offline Markus KnauerFriend
Messages: 179
Registered: July 2009
Senior Member

You are extremely fast with your update to the last nightly Wink Thank you for reporting it!

The Jetty team had their reasons to require Java 1.8, and some other projects in the Eclipse Neon development stream decided the same. But as far as I can see these requirements are only effective if someone includes those libraries into the target platform (e.g. by including the "RAP Basic Equinox Target" feature); the "RAP Runtime" doesn't contain any of the Jetty bundles and should be safe. But I assume this isn't the solution you are looking for? You are looking for a feature that pre-packages all required bundles to start a RAP application in an Equinox/Jetty environment.

Maybe we could think about delivering an older version of the Jetty bundles together with RAP; the consequence of this would be that there were two versions of Jetty in the Neon Simultaneous Release which could cause other problems, too.

Right now I'm not sure how to solve this problem in the best possible way. It would be best if you could open a bug report.

Thanks,
Markus


--

Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/

Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
Re: RAP 3.1 dependency on Java 1.8 [message #1709704 is a reply to message #1709698] Wed, 30 September 2015 13:44 Go to previous messageGo to next message
John Gymer is currently offline John GymerFriend
Messages: 279
Registered: November 2012
Location: UK
Senior Member
Thanks for the explanation Markus!
Unfortunately, I think we will have too many other restrictions meaning we cannot move to Java 1.8 yet, and therefore need RAP to use older Jetty versions.
I've raised a bug here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=478717

Thanks, John



---
Just because you can doesn't mean you should
Re: RAP 3.1 dependency on Java 1.8 [message #1709802 is a reply to message #1709698] Thu, 01 October 2015 07:45 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
On 30.09.15 15:17, Markus Knauer wrote:
> You are extremely fast with your update to the last nightly ;) Thank you
> for reporting it!
>
> The Jetty team had their reasons to require Java 1.8, and some other
> projects in the Eclipse Neon development stream decided the same. But as
> far as I can see these requirements are only effective if someone
> includes those libraries into the target platform (e.g. by including the
> "RAP Basic Equinox Target" feature); the "RAP Runtime" doesn't contain
> any of the Jetty bundles and should be safe. But I assume this isn't the
> solution you are looking for? You are looking for a feature that
> pre-packages all required bundles to start a RAP application in an
> Equinox/Jetty environment.
>
> Maybe we could think about delivering an older version of the Jetty
> bundles together with RAP; the consequence of this would be that there
> were two versions of Jetty in the Neon Simultaneous Release which could
> cause other problems, too.

I always wondered why target-platform package need to go to the release
train repository.

I think they could/should be hosted at extra p2 repositories (at least
this is what we in e(fx)clipse do to not clutter the release train
repository duplicate modules who can cause major troubles to other
projects there).

Tom
Previous Topic:JBoss Module access from RAP/OSGi Bundle
Next Topic:org.eclipse.rap.filedialog available via maven
Goto Forum:
  


Current Time: Tue Mar 19 07:27:10 GMT 2024

Powered by FUDForum. Page generated in 0.02137 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top