Hi Mark,
I wasn't aware of this request, simply because I assumed that classpath
and modulepath would allow similar arguments. Main difference: in case of
a modulepath the module-info is used if available otherwise it is
considered a auto module. When using classpath arguments, the
On 03/12/2015 19:49, Robert Scholte wrote:
After reading the specs it seems like I can only refer to a directory
containing modules. For a dependency specified in the pom.xml I could
refer to the directory (within the local repository) containing that
specific artifact. However, such
Exploded modules are useful in developer usecases. For example, I work
on a codebase with 25M+ lines of code spread over 1100+ projects. To
save time, we suppress packaging of jars when developers run builds
locally.
--
Regards,
Igor
On Fri, Dec 4, 2015, at 07:03 AM, Alan Bateman wrote:
>
> On
On 04/12/2015 12:27, Ali Ebrahimi wrote:
Just as I said in another thread post:
If we have module group concept and modules belong to same module
group loaded by same classloader then we can support splited packages.
This way each module group maps to each classloader.
This will support
Hi,
On behalf of the Apache Maven team I'm working on the Plexus Compiler[1]
to support compilation of modules and I'm struggling with the
specification of the modulepath.
According to JEP 261[1] the path of -mp is not the same as -cp
. Based of the commandline help of javac I assumed
