Avoid references to auto modules. Here's the official advice:
- Strongly advise developers never to publish, for broad use, explicit
modules that require automatic modules. That's risky: An automatic
module is unreliable, since it can depend on types on the class path,
and its name
I support this.
Also good to know is that recently we managed to make the Jigsaw team
reintroduce the NumberAtEnd[1] in the module name, which makes it again
possible that commons-lang, commons-lang2 and commons-lang3 can live next
to each other on the modulepath.
Robert
[1]
http://mai
+1 and thanks for picking this up, really appreciate it.
thanks,
Robert
On Thu, 09 Mar 2017 14:30:28 +0100, Benedikt Ritter
wrote:
Hi,
We have fixed some bugs and added two new features since CLI 1.3.1 was
released,
so I would like to release CLI 1.4.
CLI 1.4 RC1 is available for revi
Hi,
for Maven we have this issue where commandline arguments and options can
come from multiple sources and where we need to control the order of
processing these entities.
For now we've introduced our own MergedCommandLine[1], but we consider
this as a temporary workaround.
The proper sol
