Re: [m2e-users] M2Eclipse on projects requiring Java 9 Module Flags / Ad

[Fred Bricon <fbricon@xxxxxxxxx>]

In its current implementation, the modulepath is entirely inferred from the module-info.java's required modules (and their transitive dependencies, in m2e 1.9/Photon).

m2e ignores Java 9 options from the maven-compiler-plugin configuration section.

I suggest you create a sample project, try it Photon's latest CI build[1], to see where we're at, and open a bug report[2], attaching that project. 

Fred

[1] https://hudson.eclipse.org/packaging/job/photon.epp-tycho-build/lastSuccessfulBuild/artifact/org.eclipse.epp.packages/archive/

[2] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=m2e

On Wed, Feb 28, 2018 at 10:33 PM, Matthew Hall <mhall@xxxxxxxxxxxxxxx> wrote:

I have an M2Eclipse project which requires some of the irritating and seemingly pointless new Java 9 options (--add-modules ... and --add-exports ...) in order to compile.

I have added them to compilerArgs in the pom.xml. But whatever I do to add them in the Eclipse "Is Modular" editor for the JDK Libs in the Build Path, upon any kind of clean or refresh at Eclipse level or Maven project level, they seem to disappear all over again, and the project can never compile successfully because their definitions are missing.

Has anybody figured out how to deal with this problem yet?

Thanks,
Matthew
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

--

"Have you tried turning it off and on again" - The IT Crowd

And if that fails, then http://goo.gl/tnBgH5