On 27/09/2016 17:32, Peter Levart wrote:
I see. Well IMO, --add-reads should certainly not imply --add-modules
in runtime. But in compile time it would probably be convenient. In
that respect, --add-reads is similar to "requires static" a.k.a.
provided-scope dependency in Maven. javac produ
On 09/27/2016 05:41 PM, Alan Bateman wrote:
On 27/09/2016 15:45, Peter Levart wrote:
:
Perhaps it is better to separate those two things. For convenience,
there could be another option like --add-requires that would imply
both --add-reads and --add-modules...
We used to have --add-requi
On 27/09/2016 15:45, Peter Levart wrote:
:
Perhaps it is better to separate those two things. For convenience,
there could be another option like --add-requires that would imply
both --add-reads and --add-modules...
We used to have --add-requires, the reason it was replaced by
--add-reads
On 09/27/2016 12:59 PM, Alan Bateman wrote:
On 27/09/2016 11:41, Andrew Haley wrote:
Sorry, this should be simple, but I don't get it.
In this program:
import java.util.logging.Logger;
public class TestClass {
}
aph@arm64:~/SPECjvm2016/unpack$
~/hs-comp/build/linux-aarch64-normal-server
On 27/09/16 11:59, Alan Bateman wrote:
> javac could probably emit a better message here. In any case, can you
> add `--add-modules java.logging` to this. The issue is that you are
> compiling TestClass "as if" it's in the java.compiler module but that
> module does not require java.logging. The
On 27/09/2016 11:41, Andrew Haley wrote:
Sorry, this should be simple, but I don't get it.
In this program:
import java.util.logging.Logger;
public class TestClass {
}
aph@arm64:~/SPECjvm2016/unpack$
~/hs-comp/build/linux-aarch64-normal-server-release/images/jdk/bin/javac
--add-reads java
Sorry, this should be simple, but I don't get it.
In this program:
import java.util.logging.Logger;
public class TestClass {
}
aph@arm64:~/SPECjvm2016/unpack$
~/hs-comp/build/linux-aarch64-normal-server-release/images/jdk/bin/javac
--add-reads java.compiler=java.logging,java.prefs,java.deskt
