A bit more research turned up this page https://www.sitepoint.com/maven-cannot-generate-module-declaration/ in which Robert explains why my “first thought” below is a non-starter, unless the pom spec is upgraded. So it sounds now as though we are waiting on ASM to read module-info files…? Is there really nothing to be done in the meantime?
> On Aug 27, 2017, at 7:50 AM, 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
