2014/8/7 6:29 -0700, [email protected]:
> On 06/08/2014 15:08, Stephen Colebourne wrote:
>> Just wanted to express my surprise that java files are still to be
>> located in "src/.../classes". For me, most open source projects and
>> most users of Maven and other build systems, "classes" is th
On 06/08/2014 15:08, Stephen Colebourne wrote:
Just wanted to express my surprise that java files are still to be
located in "src/.../classes". For me, most open source projects and
most users of Maven and other build systems, "classes" is the name of
the *output* directory containing ".class" fi
+1. Very sensible suggestion, I think.
Cheers,
Paul
On Wed, Aug 6, 2014 at 9:08 AM, Stephen Colebourne
wrote:
> Just wanted to express my surprise that java files are still to be
> located in "src/.../classes". For me, most open source projects and
> most users of Maven and other build system
Just wanted to express my surprise that java files are still to be
located in "src/.../classes". For me, most open source projects and
most users of Maven and other build systems, "classes" is the name of
the *output* directory containing ".class" files. Having the ".java"
files in there is very co
On 06/08/2014 03:04, Weijun Wang wrote:
"modules.xml... Changes to this file will require review by Committers
to Project Jigsaw".
Shouldn't it be "Reviewers"?
From the Bylaws: "Projects that do not require any formal change review
will not have any Reviewers" and Project Jigsaw is one of tho
"modules.xml... Changes to this file will require review by Committers
to Project Jigsaw".
Shouldn't it be "Reviewers"?
"there is still a minor risk that the relationship between the new and
old locations of a file will not properly be recorded".
Could this happen?
--Max
On 8/6/2014 0:49,
FYI, here is the staging forest for JEP 201:
http://hg.openjdk.java.net/jigsaw/stage/
- Mark
New JEP Candidate: http://openjdk.java.net/jeps/201
- Mark
