Re: [equinox-dev] How does Equinox infer systemCapabilities without .pro

["Sarika Sinha" <sarika.sinha@xxxxxxxxxx>]

 

Hi Michael,

After Java 9, osgi does not maintain the profile for Java versions and PDE creates the Java profile.

Some relevant bugs:

 Bug 533052 - Investigate how PDE would retrieve Execution Environment's system packages in Java 10 and beyond 

Bug 536937 - Create JavaSE-x-systempackages.profile for java 11

 

Thanks & Regards,

Sarika

----- Original message -----
From: Mickael Istria <mistria@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx
To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] [equinox-dev] How does Equinox infer systemCapabilities without .profile files?
Date: Thu, Jul 16, 2020 3:05 PM
 

Hi all,

 

I've been deep into Tycho these days, and we managed recently to stop hardcoding the system.packages in .profile files, that's a good thing!

However, we still need those profile files for newer Java versions (JavaSE-14 and so on) because they are storing the system capabilities (eg osgi.ee: JavaSE/14.0.0). I see Equinox doesn't use those profile files at all nowadays for newer Java versions, so I imagine there is a way to dynamically get those system capabilities, and Tycho should just try to use the same strategie instead of hardcoding them. I tried to find where in the code this "inference" of system capabilities is done but didn't spot where the magic happens.

Can someone please give me a hint about where to find the code that does that?

Thanks in advance!

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/equinox-dev