yes - result of this change is as you suggest, everything shows this
warning, so we will need further discussions as to what it might mean to
make jpackage "experimental".
/Andy
On 9/15/2019 12:35 PM, Alan Bateman wrote:
On 15/09/2019 14:58, Andy Herrick wrote:
Please review the jpackage
This is a small patch to disable tracking of configuration files of
Intellij-based IDEs (.iml)
Diff:
diff -r a6f653312b19 .gitignore
--- a/.gitignoreSun Sep 15 08:41:48 2019 +0200
+++ b/.gitignoreSun Sep 15 21:11:13 2019 +0100
@@ -1,6 +1,7 @@
/build/
/dist/
/.idea/
+*.iml
Hi Martin,
These changes have caused a number of tests to break and wreaked havoc
in our CI system (as those tests get executed a lot in different
configs). The problem seems to be changes to stack use and contents:
-
On 15/09/2019 14:58, Andy Herrick wrote:
Please review the jpackage fix for bug [1] at [2].
This is a fix for the JDK-8200758-branch branch of the open sandbox
repository (jpackage).
This is the at least the first small set of changes that need to be
make to make jpackage an experimental
On 14/09/2019 21:21, Peter Firmstone wrote:
Hi Alan,
We've got a bunch of very old policy files in our test suite, so they
still had policy grants using the extension directory property. The
grant for the extension directory property was followed by a forward
slash and asterix. Oddly when
Please review the jpackage fix for bug [1] at [2].
This is a fix for the JDK-8200758-branch branch of the open sandbox
repository (jpackage).
This is the at least the first small set of changes that need to be make
to make jpackage an experimental package.
- Add flags to the build so the
Looks fine David; thanks,
-Joe
On 9/15/2019 4:49 PM, David Holmes wrote:
Bugs: https://bugs.openjdk.java.net/browse/JDK-8231033
https://bugs.openjdk.java.net/browse/JDK-8231034
webrev: http://cr.openjdk.java.net/~dholmes/8231033-8231034/webrev/
(inline below)
A bunch of mainly
Sorry about the breakage. In retrospect, this is one jsr166 integration
where we should have run more tests from other areas of the jdk.
Especially monitoring tests are sensitive to implementation changes in
j.u.c.locks.
(but we've never run nsk tests)
On Sun, Sep 15, 2019 at 3:14 PM David
Bugs: https://bugs.openjdk.java.net/browse/JDK-8231033
https://bugs.openjdk.java.net/browse/JDK-8231034
webrev: http://cr.openjdk.java.net/~dholmes/8231033-8231034/webrev/
(inline below)
A bunch of mainly management tests (mostly in hotspot repo) are failing
after the JSR-166 refresh to
Thanks Joe. Will push once CI testing is verified.
David
On 16/09/2019 9:54 am, Joe Darcy wrote:
Looks fine David; thanks,
-Joe
On 9/15/2019 4:49 PM, David Holmes wrote:
Bugs: https://bugs.openjdk.java.net/browse/JDK-8231033
https://bugs.openjdk.java.net/browse/JDK-8231034
webrev:
10 matches
Mail list logo