This is a very good proposal. My only suggestion is to extend
javax.tools CompilationTask API to take modulepath map as in-memory
parameter. Not a big deal, but it'll be silly to write properties
file to disk for it to be immediately read by the code executed in
the same jvm.
--
Regards,
Igor
module-info on classpath is ignored. That's also the reason why I can run
surefire with my module-info enriched project.
If you add a jar without module-info to the module-path, it is considered
an automodule, i.e exports all packages and requires all available modules.
This kind of informati
So if I do not implement module-info.java in surefire booter, everything
would be same as in the old JVM?
What if a user has module-info.class in one of his jar files which appears
in Class-Path of surefire's MANIFEST.MF?
Anyway we should include Oracle guys into our discussion.
What influence th
According to the JDK ticket, Alan says: "anything that implements "module
path" would need to support this." I assumed this also means java.exe. The
ticket also states they want to get away from "long command lines". Based
on these remarks, it should be affecting forking too.
On Jan 9, 2016 10:57 A
a.
Regarding execution of forked JVM in Surefire it has nothing to do with
javac, nothing but java.
Regarding building forked jar, then yes this may have an impact because we
create jar file which contains manifetst having Class-Path.
b.
Is the classpath in manifest going to be deprecated or remov
Hi Paul,
thanks for your response.
I'm not sure if I follow you with the forking problem. I guess you're
talking about the fork option of surefire.
Maybe one of the active surefire committers can explain how classpaths are
handled right now and if this has a conflict with this proposal.
Bas
It sounds like Maven will have to generate many .properties file in a build.
1) Modules to compile main source
2) Modules to compile test source
3) Modules to execute tests
4) And what about forking?
I am concerned #4 is going to create issues unless the .properties file
name is unique enough. Per
FYI, a new idea to solve our modulepath issue.
Any feedback is appreciated.
thanks,
Robert
Forwarded Message Subject:Specifying module paths
Date: Thu, 07 Jan 2016 15:39:43 -0800
From: Jonathan Gibbons
To: jigsaw-dev
This is a follow-up to some of the recent em