Eclipse Community Forums: Oomph » Importing projects with different Java-Version

Home » Eclipse Projects » Oomph » Importing projects with different Java-Version

Importing projects with different Java-Version [message #1714281]

Wed, 11 November 2015 05:03

Eclipse User

Given i have a setup task , which imports multiple projects. Each of them requires a certain java version.

My idea would be to create variables with paths to different java JDKs and then tell the project import task to set the appropriate java path for a specific project.

Now my question is, is it possible to tell the projects import task to set the java path for a specific project ?

[Updated on: Wed, 11 November 2015 05:04] by Moderator

Re: Importing projects with different Java-Version [message #1714290 is a reply to message #1714281]

Wed, 11 November 2015 07:06

Eclipse User

Maksim,

Comments below.

On 11/11/2015 11:03 AM, Maksim Melnik wrote:
> Given i have a project consisting of multiple projects. Each of them
> requires a certain java version.
Typically that's a minimum requirement, not a strict requirement.
>
> My idea would be to create variables with paths to different java JDKs
> and then tell the project import task to set the appropriate java path
> for a specific project.
How is the project import task involved? Isn't a JRE task sufficient?
>
> Now my question is, is it possible to tell the projects import task to
> set the java path for a specific project ?
Normally projects specify a BREE and based on the available JREs they
are bound to the best match.

Re: Importing projects with different Java-Version [message #1714299 is a reply to message #1714290]

Wed, 11 November 2015 09:42

Eclipse User

So you want to say, that if I input several JREs as JRE tasks, then each project will be bound to the best match ?

Re: Importing projects with different Java-Version [message #1714313 is a reply to message #1714299]

Wed, 11 November 2015 11:46

Eclipse User

Maksim,

Yes, that's generally JDT's behavior. It's very hard to find old JDKs
these days though, so I'm not sure specifically what your concern is.
Most people just get a JDK/JRE 1.8 and use it for everything. There
are EE profiles that can check that you aren't using features
(methods/classes) of a newer JRE that aren't present in the BREE's exact
JRE.

On 11/11/2015 3:42 PM, Maksim Melnik wrote:
> So you want to say, that if I input several JREs as JRE tasks, then
> each project will be bound to the best match ?

Re: Importing projects with different Java-Version [message #1714315 is a reply to message #1714313]

Wed, 11 November 2015 11:53

Eclipse User

Hi,

I think if a project needs a specific JRE then that should be configured in the project's Properties dialog (right-click
on the project). I've attached a screenshot...

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 11.11.2015 um 17:46 schrieb Ed Merks:
> Maksim,
>
> Yes, that's generally JDT's behavior. It's very hard to find old JDKs these days though, so I'm not sure
> specifically what your concern is. Most people just get a JDK/JRE 1.8 and use it for everything. There are EE
> profiles that can check that you aren't using features (methods/classes) of a newer JRE that aren't present in the
> BREE's exact JRE.
>
>
> On 11/11/2015 3:42 PM, Maksim Melnik wrote:
>> So you want to say, that if I input several JREs as JRE tasks, then each project will be bound to the best match ?
>

Attachment: alternate-jre.png
(Size: 81.70KB, Downloaded 206 times)

Previous Topic:	Oomph Version Management - How to ?
Next Topic:	How-to create a Setup model which allows to switch between streams and change Xtext version?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 16 16:03:12 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter