On 2014-02-27 22:33, Phil Race wrote:
Hi,
Leaving aside jigsaw, and regardless of whether they are modifiable,
the question as to whether at runtime they should live in rt.jar or
jre/lib
is a separate question than where they would live in the source tree
and one does not necessarily follow th
Phil,
Just on Project Jigsaw and moving to a modular JDK then we've been doing
preparatory work for this for several years (it had its own JEP in JDK 8
for example). There isn't a JEP yet proposing a Modular JDK but
hopefully soon. In the mean-time I think we have to continue the
clean-up and
Hi,
Leaving aside jigsaw, and regardless of whether they are modifiable,
the question as to whether at runtime they should live in rt.jar or jre/lib
is a separate question than where they would live in the source tree
and one does not necessarily follow the other.
You seem to be touching on the
Hi Phil,
Is psfont*.properties* file more of a resource file? Is there any
reason (or specification) that psfont*.properties has to be in JRE/lib
directory? One potential reason might be the startup performance (warm
start/cold start) to avoid opening a jar file? They don't look like a
user-
Magnus,
I completely understand that the content of the files and the runtime
behaviour aren't affected, but logically you'd want to put things together,
not spread out across the source tree. Then its much easier for people to
understand what uses what.
If a jigsaw build somehow can't cope with
Phil,
First of all, note that this is a change in build only. This change will not
affect the source code in question, nor how it is executed. The properties
files will end up in the very same location as a result of the build, wether
with or without this patch. Hence, there is no need to run a
