Hi Robert, That sounds great. Any idea on timing of the release? What about the surefire plugin? Is there something I can do to help? I am actively working on Java 9 issues in a few projects, including both the module system and multi-release jars, so I am very motivated to do what I can to help maven get there.
Thanks, Russ > On Aug 27, 2017, at 8:38 AM, Robert Scholte <rfscho...@apache.org> wrote: > > Hi Russ, > > this is how it works: > in case there's a module descriptor, the module-path with be used. With the > help of plexus-java it is possible to divide all jars over the module-path > and classpath. This mechanism is implemented in the maven-compiler-plugin > (will do an official release soon with the latest improvements), other > plugins can/should use this too. > > This means that you actually don't need to change anything in your pom.xml. > With the module descriptor and all the dependencies there's enough > information to decide which jars belong on the modulepath and which on the > classpath. So in the end there's no need for new scopes anymore, although > that was my first thought as well. > > To create an installer, I think you're referring to JLink. Karl Heinz is > preparing the maven-jlink-plugin. > > thanks, > Robert > > On Sun, 27 Aug 2017 13:50:46 +0200, Russell Gold <russell.g...@oracle.com> > wrote: > >> I’m sure this must have been described somewhere; is there an overall >> direction document for supporting the java platform module system? >> >> case 1) >> >> I want to compile against another project on the module path rather than the >> class path. I do this in order to ensure compile-time checking for attempts >> to compile against non-exported packages. >> >> case 2) >> >> I want to test against another project on the module path. This would allow >> me to catch reflective access attempts against that module’s internals >> >> case 3) >> >> I want to use the module dependencies to create an installer, with the >> dependent modules on the module path. In theory, if Maven understands the >> above 2 cases, it would also be able to verify the requires clauses in my >> project’s module-info. >> >> So how will we be doing this in maven? Is it already supported? My first >> thought was that we need two new scopes: module (case 1) and module-test >> (case 2), but has this already been planned? >> >> Thanks, >> Russ >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
