Hi Tom,
I think that running the PDE project should run without module info with java9. I am not sure why
module-info is required for javafx access.
Right now, module-info and OSGI's presence together is not defined properly and hence the errors
are expected.
>I guess (in future) there have to be another way because defining a
>module-info.java means i really want to define a Java9-Module which i
>don't want, all I want is to make my code compile and then run inside an
>OSGi-Application who runs as an unnamed-module and hence is able to
>access all java-modules by default.
For both OSGI and module info to co-exist, the behaviour needs to be defined properly -
whether OSGI will be just a dummy or module info will be just a dummy or how OSGI will interact
with module-info.
Meanwhile can you please open a bug on PDE so that I can investigate this scenario further.
Having said that at this point, the behaviour is expected and that bug can serve as a
placeholder of what possible things can be done for that.
Thanks and Regards,
Vikas
Sent by: jdt-core-dev-bounces@xxxxxxxxxxx
Date: 01/17/2017 02:33PM
Subject: [jdt-core-dev] module-info.java in PDE-Projects
Hi,
To gain access to JavaFX in PDE managed projects I have to create a
module-info.java file.
At the very moment I do that all of the classes provided through the
PDE-Classpath-Container fail to resolve (note auto-complete still shows
them, navigating to them still works, ...).
All imports show "The import ... cannot be resolved". Too me it looks
like as if a module-info.java is in the projects it's the one and only
authority to define the classpath of a project and other
classpath-containers are not taken into account any more.
Am I right on that?
Is that by design?
Is there another way to gain access to modules you don't take into
account by default beside adding a module-info.java?
I guess (in future) there have to be another way because defining a
module-info.java means i really want to define a Java9-Module which i
don't want, all I want is to make my code compile and then run inside an
OSGi-Application who runs as an unnamed-module and hence is able to
access all java-modules by default.
Tom
--
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
_______________________________________________
jdt-core-dev mailing list
jdt-core-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-core-dev
