From rory.odonnell at oracle.com Mon Nov 2 08:51:32 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Mon, 2 Nov 2015 08:51:32 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: <5634C884.6040302@oracle.com> References: <5634C884.6040302@oracle.com> Message-ID: <56372414.7010605@oracle.com> I can't find a bug in Gradle's JIRA on this issue, Mani do you want to log an issue there ? Rgds,Rory On 31/10/2015 13:56, Alan Bateman wrote: > On 31/10/2015 12:50, Mani Sarkar wrote: >> Hi Rory, >> >> Do you know of a version of Gradle or a EA version which is JDK 9 >> Jigsaw compatible, we get these failures when building: >> >> https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console >> >> > Caused by: java.lang.IllegalAccessException: class > org.gradle.internal.reflect.DirectInstantiator cannot access class > com.sun.tools.javac.api.JavacTool (in module jdk.compiler) because > module jdk.compiler does not export package com.sun.tools.javac.api to > > at > org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:49) > ... 86 more > > We should at least check if there is a bug in the Gradle JIRA for > this. It can be worked around by configuring the compileJava options > to fork javac but you might not want to do that. > > The other issue with Gradle that we know about is the > ClassCastException when attempting to run tests, this is tracked here: > https://issues.gradle.org/browse/GRADLE-3287 > > -Alan. > -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland From Alan.Bateman at oracle.com Mon Nov 2 09:05:23 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 2 Nov 2015 09:05:23 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: References: <5634C884.6040302@oracle.com> <56372414.7010605@oracle.com> Message-ID: <56372753.6010702@oracle.com> On 02/11/2015 08:56, C?dric Champeau wrote: > BTW, Groovy itself is not compatible with Jigsaw, so my guess would be > that even if Gradle fixed this, you would have different errors > because Gradle uses Groovy. What is possible today is to run Gradle on > Java 9 non jigsaw, and compile using Java 9 Jigsaw. > > Jochen sent an email on jigsaw-dev a few weeks ago ("Groovy with > Jigsaw") but as far as I understand, there's no clear understanding of > the problem/solutions so far. There was one specific issue in that thread, it was a VerifyError that stemmed from Guava overriding java.lang.reflect.AccessibleObject.setAccessible. That issue was resolved at the time and I don't think there were any other specific issues on that thread. There was of course the general issue that Groovy seems to access or wrap types in non-exported packages but we don't have a solution to that except via the command-line -XaddExports. -Alan. From Alan.Bateman at oracle.com Mon Nov 2 10:24:50 2015 From: Alan.Bateman at oracle.com (Alan Bateman) Date: Mon, 2 Nov 2015 10:24:50 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: References: <5634C884.6040302@oracle.com> <56372414.7010605@oracle.com> <56372753.6010702@oracle.com> Message-ID: <563739F2.2030002@oracle.com> On 02/11/2015 09:58, C?dric Champeau wrote: > > I think this is the particular issue Jochen is very worried about. We > should think about the consequences of it. What does it mean to be > forced to use -XaddExports. It is at least unclear to me. What would > be catastrophic is releasing Jigsaw and realizing that we killed > Groovy because it cannot use modules without, for example, disabling > all kind of security. Uwe Schindler has created a bug on this topic here: https://issues.apache.org/jira/browse/GROOVY-7587 It makes me wonder if Groovy has ever been used with a security manager as it seems to wrap or need access to all JDK-internal types. -Alan. From martijnverburg at gmail.com Mon Nov 2 11:31:47 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Mon, 2 Nov 2015 11:31:47 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Hey Mani, Ah, I wondered where that was being hosted. You're happy to move that to the AdoptOpenJDK repo post Devoxx correct? I've added a link to this Kit in the wiki and have also added the OpenJDK IRC channel link to the wiki as well. Cheers, Martijn On 31 October 2015 at 09:34, Mani Sarkar wrote: > Hi all, > > I have put together this page on how to ... > > > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html > > As a community we should feel free to amend the contents as per what > really is meant by contributions. > > Anything incorrect or missing - feel free to report here or create a pull > request (see > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html > ). > > Thanks for reading and contributing. > > Cheers, > Mani > > -- > @theNeomatrix369 * | **Blog > ** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > * | **Bitbucket > * * | **Github > * * | **LinkedIn > * > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blackdrag at gmx.org Mon Nov 2 12:55:45 2015 From: blackdrag at gmx.org (Jochen Theodorou) Date: Mon, 2 Nov 2015 13:55:45 +0100 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: <563739F2.2030002@oracle.com> References: <5634C884.6040302@oracle.com> <56372414.7010605@oracle.com> <56372753.6010702@oracle.com> <563739F2.2030002@oracle.com> Message-ID: <56375D51.6020101@gmx.org> On 02.11.2015 11:24, Alan Bateman wrote: [...] > Uwe Schindler has created a bug on this topic here: > > https://issues.apache.org/jira/browse/GROOVY-7587 > > It makes me wonder if Groovy has ever been used with a security manager > as it seems to wrap or need access to all JDK-internal types. This impression is wrong, Groovy does not need access to all JDK-internal types. But this is a dynamic language at heart. If you do not have a static type, then the runtime type is what counts, and that is the exact type, which is sometime an internal JDK type. It means Groovy has to do the same thing it has to do when a security manager doesn't like access to this class, which is to not use the specific class/method, but the super class information... or the information of that super class.. in worst case this will be Object, which means only method from Object can be called using Groovy in that case. The current state is, that this issue is now fixed. The example scripts in the issue are working. That does not mean we can now run the build on jigsaw of course. bye Jochen From sadhak001 at gmail.com Mon Nov 2 22:23:38 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Mon, 2 Nov 2015 22:23:38 +0000 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: <56372414.7010605@oracle.com> References: <5634C884.6040302@oracle.com> <56372414.7010605@oracle.com> Message-ID: Hi Rory, TestNG has an alternative build system which we will try to use to build it using the Jigsaw binary. How do you report such bugs to Gradle / Groovy ? Is it simpler if you reported to them on their mailing list ? Let me know what works best, this is fairly important as other Gradle users might have similar issues. Cheers, Mani On Mon, Nov 2, 2015 at 8:51 AM, Rory O'Donnell wrote: > I can't find a bug in Gradle's JIRA on this issue, Mani do you want to log > an issue there ? > > Rgds,Rory > > > On 31/10/2015 13:56, Alan Bateman wrote: > >> On 31/10/2015 12:50, Mani Sarkar wrote: >> >>> Hi Rory, >>> >>> Do you know of a version of Gradle or a EA version which is JDK 9 Jigsaw >>> compatible, we get these failures when building: >>> >>> >>> https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console >>> >>> Caused by: java.lang.IllegalAccessException: class >> org.gradle.internal.reflect.DirectInstantiator cannot access class >> com.sun.tools.javac.api.JavacTool (in module jdk.compiler) because module >> jdk.compiler does not export package com.sun.tools.javac.api to > module @b7f23d9> >> at >> org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:49) >> ... 86 more >> >> We should at least check if there is a bug in the Gradle JIRA for this. >> It can be worked around by configuring the compileJava options to fork >> javac but you might not want to do that. >> >> The other issue with Gradle that we know about is the ClassCastException >> when attempting to run tests, this is tracked here: >> https://issues.gradle.org/browse/GRADLE-3287 >> >> -Alan. >> >> > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Mon Nov 2 22:25:59 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Mon, 2 Nov 2015 22:25:59 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Martijn, I'm in conversation with the guys about moving it, and after Devoxx BE is a better move I think although I would have liked it to be earlier. On a more important note, I was wondering if the contents of the pages I shared were good, if not, happy to change them so that adoptors get the right info. Cheers, Mani On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg wrote: > Hey Mani, > > Ah, I wondered where that was being hosted. You're happy to move that to > the AdoptOpenJDK repo post Devoxx correct? I've added a link to this Kit > in the wiki and have also added the OpenJDK IRC channel link to the wiki as > well. > > Cheers, > Martijn > > On 31 October 2015 at 09:34, Mani Sarkar wrote: > >> Hi all, >> >> I have put together this page on how to ... >> >> >> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >> >> As a community we should feel free to amend the contents as per what >> really is meant by contributions. >> >> Anything incorrect or missing - feel free to report here or create a pull >> request (see >> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >> ). >> >> Thanks for reading and contributing. >> >> Cheers, >> Mani >> >> -- >> @theNeomatrix369 * | **Blog >> ** | *LJC Associate & LJC Advocate >> (@adoptopenjdk & @adoptajsr programs) >> *Meet-a-Project - *MutabilityDetector >> * | **Bitbucket >> * * | **Github >> * * | **LinkedIn >> * >> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >> >> *Don't chase success, rather aim for "Excellence", and success will come >> chasing after you!* >> > > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Tue Nov 3 00:39:36 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 3 Nov 2015 00:39:36 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Once you make the move it'll get more eyes and more PRs will start to arrive (much like Jitwatch and jcountdown I suspect). Is there someone in this list who is fairly new and will go through Mani's doc? Cheers, Martijn On Monday, 2 November 2015, Mani Sarkar wrote: > Martijn, > > I'm in conversation with the guys about moving it, and after Devoxx BE is > a better move I think although I would have liked it to be earlier. > > On a more important note, I was wondering if the contents of the pages I > shared were good, if not, happy to change them so that adoptors get the > right info. > > Cheers, > Mani > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg > wrote: > >> Hey Mani, >> >> Ah, I wondered where that was being hosted. You're happy to move that to >> the AdoptOpenJDK repo post Devoxx correct? I've added a link to this Kit >> in the wiki and have also added the OpenJDK IRC channel link to the wiki as >> well. >> >> Cheers, >> Martijn >> >> On 31 October 2015 at 09:34, Mani Sarkar > > wrote: >> >>> Hi all, >>> >>> I have put together this page on how to ... >>> >>> >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >>> >>> As a community we should feel free to amend the contents as per what >>> really is meant by contributions. >>> >>> Anything incorrect or missing - feel free to report here or create a >>> pull request (see >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >>> ). >>> >>> Thanks for reading and contributing. >>> >>> Cheers, >>> Mani >>> >>> -- >>> @theNeomatrix369 * | **Blog >>> ** | *LJC Associate & LJC Advocate >>> (@adoptopenjdk & @adoptajsr programs) >>> *Meet-a-Project - *MutabilityDetector >>> * | **Bitbucket >>> * * | **Github >>> * * | **LinkedIn >>> * >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> >>> *Don't chase success, rather aim for "Excellence", and success will come >>> chasing after you!* >>> >> >> > > > -- > @theNeomatrix369 * | **Blog > ** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > * | **Bitbucket > * * | **Github > * * | **LinkedIn > * > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!* > -- Cheers, Martijn (Sent from Gmail Mobile) -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Tue Nov 3 09:31:15 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 3 Nov 2015 09:31:15 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: I think there should also be clear guidance on how to submit your first patch for a small, low-impact change (like a code clean up). Over time we want more people to gain Author+ status in the various projects, especially around safer parts of OpenJDK (e.g. Not Hotspot) Cheers, Martijn On 3 November 2015 at 06:07, Mohan Radhakrishnan < radhakrishnan.mohan at gmail.com> wrote: > I read the contribution procedure. > > Are these basically the avenues ? > > 1. One could individually participate in JCP spec. activities without > guidance depending on one's skill level. > 2. Participate along with the local JUG. > 3. Contribute to one of the OpenJDK projects like JITWatch etc. > 4. Contribute to documentation. > > Thanks, > Mohan > > On 3 November 2015 at 06:09, Martijn Verburg > wrote: > > > Once you make the move it'll get more eyes and more PRs will start to > > arrive (much like Jitwatch and jcountdown I suspect). > > > > Is there someone in this list who is fairly new and will go through > Mani's > > doc? > > > > Cheers, > > Martijn > > > > On Monday, 2 November 2015, Mani Sarkar wrote: > > > > > Martijn, > > > > > > I'm in conversation with the guys about moving it, and after Devoxx BE > is > > > a better move I think although I would have liked it to be earlier. > > > > > > On a more important note, I was wondering if the contents of the pages > I > > > shared were good, if not, happy to change them so that adoptors get the > > > right info. > > > > > > Cheers, > > > Mani > > > > > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < > > martijnverburg at gmail.com > > > > wrote: > > > > > >> Hey Mani, > > >> > > >> Ah, I wondered where that was being hosted. You're happy to move that > > to > > >> the AdoptOpenJDK repo post Devoxx correct? I've added a link to this > > Kit > > >> in the wiki and have also added the OpenJDK IRC channel link to the > > wiki as > > >> well. > > >> > > >> Cheers, > > >> Martijn > > >> > > >> On 31 October 2015 at 09:34, Mani Sarkar > >> > wrote: > > >> > > >>> Hi all, > > >>> > > >>> I have put together this page on how to ... > > >>> > > >>> > > >>> > > > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html > > >>> > > >>> As a community we should feel free to amend the contents as per what > > >>> really is meant by contributions. > > >>> > > >>> Anything incorrect or missing - feel free to report here or create a > > >>> pull request (see > > >>> > > > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html > > >>> ). > > >>> > > >>> Thanks for reading and contributing. > > >>> > > >>> Cheers, > > >>> Mani > > >>> > > >>> -- > > >>> @theNeomatrix369 * | **Blog > > >>> ** | *LJC Associate & LJC > > Advocate > > >>> (@adoptopenjdk & @adoptajsr programs) > > >>> *Meet-a-Project - *MutabilityDetector > > >>> * | **Bitbucket > > >>> * * | **Github > > >>> * * | **LinkedIn > > >>> * > > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > >>> > > >>> *Don't chase success, rather aim for "Excellence", and success will > > come > > >>> chasing after you!* > > >>> > > >> > > >> > > > > > > > > > -- > > > @theNeomatrix369 * | **Blog > > > ** | *LJC Associate & LJC > Advocate > > > (@adoptopenjdk & @adoptajsr programs) > > > *Meet-a-Project - *MutabilityDetector > > > * | **Bitbucket > > > * * | **Github > > > * * | **LinkedIn > > > * > > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > > > > > *Don't chase success, rather aim for "Excellence", and success will > come > > > chasing after you!* > > > > > > > > > -- > > Cheers, Martijn (Sent from Gmail Mobile) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From blackdrag at gmx.org Tue Nov 3 10:01:12 2015 From: blackdrag at gmx.org (Jochen Theodorou) Date: Tue, 3 Nov 2015 11:01:12 +0100 Subject: TestNG build failing with JDK9 Jigsaw due to Gradle In-Reply-To: References: <5634C884.6040302@oracle.com> <56372414.7010605@oracle.com> Message-ID: <563885E8.80101@gmx.org> Hi, Jochen here, not Rory, but Groovy maintainer ;) So for Groovy reporting on the mailing list is good, if you also want to discuss the bug a bit there. If you really only want to report it, then you can just write it in the bug tracker. Of course Gradle is Gradle and Groovy is Groovy bye Jochen On 02.11.2015 23:23, Mani Sarkar wrote: > Hi Rory, > > TestNG has an alternative build system which we will try to use to build > it using the Jigsaw binary. > > How do you report such bugs to Gradle / Groovy ? Is it simpler if you > reported to them on their mailing list ? Let me know what works best, > this is fairly important as other Gradle users might have similar issues. > > Cheers, > Mani > > On Mon, Nov 2, 2015 at 8:51 AM, Rory O'Donnell > wrote: > > I can't find a bug in Gradle's JIRA on this issue, Mani do you want > to log an issue there ? > > Rgds,Rory > > > On 31/10/2015 13:56, Alan Bateman wrote: > > On 31/10/2015 12:50, Mani Sarkar wrote: > > Hi Rory, > > Do you know of a version of Gradle or a EA version which is > JDK 9 Jigsaw compatible, we get these failures when building: > > https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/5/console > > > Caused by: java.lang.IllegalAccessException: class > org.gradle.internal.reflect.DirectInstantiator cannot access > class com.sun.tools.javac.api.JavacTool (in module jdk.compiler) > because module jdk.compiler does not export package > com.sun.tools.javac.api to > at > org.gradle.internal.reflect.DirectInstantiator.newInstance(DirectInstantiator.java:49) > ... 86 more > > We should at least check if there is a bug in the Gradle JIRA > for this. It can be worked around by configuring the compileJava > options to fork javac but you might not want to do that. > > The other issue with Gradle that we know about is the > ClassCastException when attempting to run tests, this is tracked > here: > https://issues.gradle.org/browse/GRADLE-3287 > > -Alan. > > > -- > Rgds,Rory O'Donnell > Quality Engineering Manager > Oracle EMEA , Dublin, Ireland > > > > > -- > @theNeomatrix369 * | **Blog > ** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > * | **Bitbucket > * * | **Github > ** | **LinkedIn > * > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > */Don't chase success, rather aim for "Excellence", and success will > come chasing after you!/* From martijnverburg at gmail.com Tue Nov 3 15:19:28 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 3 Nov 2015 15:19:28 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Yes, it pays to discuss the change *before* you submit it, you'd be surprised why certain things are the way they are :-) Cheers, Martijn On 3 November 2015 at 12:02, Mohan Radhakrishnan < radhakrishnan.mohan at gmail.com> wrote: > That is interesting. They do accept such small changes then. > > Thanks, > Mohan > > On 3 November 2015 at 15:01, Martijn Verburg > wrote: > >> I think there should also be clear guidance on how to submit your first >> patch for a small, low-impact change (like a code clean up). Over time we >> want more people to gain Author+ status in the various projects, especially >> around safer parts of OpenJDK (e.g. Not Hotspot) >> >> Cheers, >> Martijn >> >> On 3 November 2015 at 06:07, Mohan Radhakrishnan < >> radhakrishnan.mohan at gmail.com> wrote: >> >>> I read the contribution procedure. >>> >>> Are these basically the avenues ? >>> >>> 1. One could individually participate in JCP spec. activities without >>> guidance depending on one's skill level. >>> 2. Participate along with the local JUG. >>> 3. Contribute to one of the OpenJDK projects like JITWatch etc. >>> 4. Contribute to documentation. >>> >>> Thanks, >>> Mohan >>> >>> On 3 November 2015 at 06:09, Martijn Verburg >>> wrote: >>> >>> > Once you make the move it'll get more eyes and more PRs will start to >>> > arrive (much like Jitwatch and jcountdown I suspect). >>> > >>> > Is there someone in this list who is fairly new and will go through >>> Mani's >>> > doc? >>> > >>> > Cheers, >>> > Martijn >>> > >>> > On Monday, 2 November 2015, Mani Sarkar wrote: >>> > >>> > > Martijn, >>> > > >>> > > I'm in conversation with the guys about moving it, and after Devoxx >>> BE is >>> > > a better move I think although I would have liked it to be earlier. >>> > > >>> > > On a more important note, I was wondering if the contents of the >>> pages I >>> > > shared were good, if not, happy to change them so that adoptors get >>> the >>> > > right info. >>> > > >>> > > Cheers, >>> > > Mani >>> > > >>> > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < >>> > martijnverburg at gmail.com >>> > > > wrote: >>> > > >>> > >> Hey Mani, >>> > >> >>> > >> Ah, I wondered where that was being hosted. You're happy to move >>> that >>> > to >>> > >> the AdoptOpenJDK repo post Devoxx correct? I've added a link to >>> this >>> > Kit >>> > >> in the wiki and have also added the OpenJDK IRC channel link to the >>> > wiki as >>> > >> well. >>> > >> >>> > >> Cheers, >>> > >> Martijn >>> > >> >>> > >> On 31 October 2015 at 09:34, Mani Sarkar >> > >> > wrote: >>> > >> >>> > >>> Hi all, >>> > >>> >>> > >>> I have put together this page on how to ... >>> > >>> >>> > >>> >>> > >>> >>> > >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >>> > >>> >>> > >>> As a community we should feel free to amend the contents as per >>> what >>> > >>> really is meant by contributions. >>> > >>> >>> > >>> Anything incorrect or missing - feel free to report here or create >>> a >>> > >>> pull request (see >>> > >>> >>> > >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >>> > >>> ). >>> > >>> >>> > >>> Thanks for reading and contributing. >>> > >>> >>> > >>> Cheers, >>> > >>> Mani >>> > >>> >>> > >>> -- >>> > >>> @theNeomatrix369 * | **Blog >>> > >>> ** | *LJC Associate & LJC >>> > Advocate >>> > >>> (@adoptopenjdk & @adoptajsr programs) >>> > >>> *Meet-a-Project - *MutabilityDetector >>> > >>> * | **Bitbucket >>> > >>> * * | **Github >>> > >>> * * | **LinkedIn >>> > >>> * >>> > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> > >>> >>> > >>> *Don't chase success, rather aim for "Excellence", and success will >>> > come >>> > >>> chasing after you!* >>> > >>> >>> > >> >>> > >> >>> > > >>> > > >>> > > -- >>> > > @theNeomatrix369 * | **Blog >>> > > ** | *LJC Associate & LJC >>> Advocate >>> > > (@adoptopenjdk & @adoptajsr programs) >>> > > *Meet-a-Project - *MutabilityDetector >>> > > * | **Bitbucket >>> > > * * | **Github >>> > > * * | **LinkedIn >>> > > * >>> > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> > > >>> > > *Don't chase success, rather aim for "Excellence", and success will >>> come >>> > > chasing after you!* >>> > > >>> > >>> > >>> > -- >>> > Cheers, Martijn (Sent from Gmail Mobile) >>> > >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Wed Nov 4 11:46:23 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Wed, 4 Nov 2015 11:46:23 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Hi Mohan, That is good advice yes - the IRC channel for the JSRs (different programme) hasn't really worked. The IRC channel for the official openjdk is actually quite active. Cheers, Martijn On 4 November 2015 at 11:35, Mohan Radhakrishnan < radhakrishnan.mohan at gmail.com> wrote: > If you're interested in a particular area but don't have any specific >> ideas about what to do then feel free to post a query to the appropriate >> Group or Projectdevelopment list to ask >> for suggestions that match your skills and knowledge. A list of all the >> Groups and Projects >> may be found at the left-hand >> side of this page; you are more than welcome to subscribe >> to any of their mailing lists. A >> complete list of all of the Groups, Projects, people and their roles may be >> found in the census . > > > This is the best advice in http://openjdk.java.net/contribute/. > One could regularly participate in the IRC discussion of JSR;s. I tried > that. But even then generally the close-knit group may meet at conferences > that all cannot pay to attend. > > Thanks, > Mohan > > On 3 November 2015 at 20:49, Martijn Verburg > wrote: > >> Yes, it pays to discuss the change *before* you submit it, you'd be >> surprised why certain things are the way they are :-) >> >> Cheers, >> Martijn >> >> On 3 November 2015 at 12:02, Mohan Radhakrishnan < >> radhakrishnan.mohan at gmail.com> wrote: >> >>> That is interesting. They do accept such small changes then. >>> >>> Thanks, >>> Mohan >>> >>> On 3 November 2015 at 15:01, Martijn Verburg >>> wrote: >>> >>>> I think there should also be clear guidance on how to submit your first >>>> patch for a small, low-impact change (like a code clean up). Over time we >>>> want more people to gain Author+ status in the various projects, especially >>>> around safer parts of OpenJDK (e.g. Not Hotspot) >>>> >>>> Cheers, >>>> Martijn >>>> >>>> On 3 November 2015 at 06:07, Mohan Radhakrishnan < >>>> radhakrishnan.mohan at gmail.com> wrote: >>>> >>>>> I read the contribution procedure. >>>>> >>>>> Are these basically the avenues ? >>>>> >>>>> 1. One could individually participate in JCP spec. activities without >>>>> guidance depending on one's skill level. >>>>> 2. Participate along with the local JUG. >>>>> 3. Contribute to one of the OpenJDK projects like JITWatch etc. >>>>> 4. Contribute to documentation. >>>>> >>>>> Thanks, >>>>> Mohan >>>>> >>>>> On 3 November 2015 at 06:09, Martijn Verburg >>>> > >>>>> wrote: >>>>> >>>>> > Once you make the move it'll get more eyes and more PRs will start to >>>>> > arrive (much like Jitwatch and jcountdown I suspect). >>>>> > >>>>> > Is there someone in this list who is fairly new and will go through >>>>> Mani's >>>>> > doc? >>>>> > >>>>> > Cheers, >>>>> > Martijn >>>>> > >>>>> > On Monday, 2 November 2015, Mani Sarkar wrote: >>>>> > >>>>> > > Martijn, >>>>> > > >>>>> > > I'm in conversation with the guys about moving it, and after >>>>> Devoxx BE is >>>>> > > a better move I think although I would have liked it to be earlier. >>>>> > > >>>>> > > On a more important note, I was wondering if the contents of the >>>>> pages I >>>>> > > shared were good, if not, happy to change them so that adoptors >>>>> get the >>>>> > > right info. >>>>> > > >>>>> > > Cheers, >>>>> > > Mani >>>>> > > >>>>> > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < >>>>> > martijnverburg at gmail.com >>>>> > > > wrote: >>>>> > > >>>>> > >> Hey Mani, >>>>> > >> >>>>> > >> Ah, I wondered where that was being hosted. You're happy to move >>>>> that >>>>> > to >>>>> > >> the AdoptOpenJDK repo post Devoxx correct? I've added a link to >>>>> this >>>>> > Kit >>>>> > >> in the wiki and have also added the OpenJDK IRC channel link to >>>>> the >>>>> > wiki as >>>>> > >> well. >>>>> > >> >>>>> > >> Cheers, >>>>> > >> Martijn >>>>> > >> >>>>> > >> On 31 October 2015 at 09:34, Mani Sarkar >>>> > >> > wrote: >>>>> > >> >>>>> > >>> Hi all, >>>>> > >>> >>>>> > >>> I have put together this page on how to ... >>>>> > >>> >>>>> > >>> >>>>> > >>> >>>>> > >>>>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >>>>> > >>> >>>>> > >>> As a community we should feel free to amend the contents as per >>>>> what >>>>> > >>> really is meant by contributions. >>>>> > >>> >>>>> > >>> Anything incorrect or missing - feel free to report here or >>>>> create a >>>>> > >>> pull request (see >>>>> > >>> >>>>> > >>>>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >>>>> > >>> ). >>>>> > >>> >>>>> > >>> Thanks for reading and contributing. >>>>> > >>> >>>>> > >>> Cheers, >>>>> > >>> Mani >>>>> > >>> >>>>> > >>> -- >>>>> > >>> @theNeomatrix369 * | >>>>> **Blog >>>>> > >>> ** | *LJC Associate & LJC >>>>> > Advocate >>>>> > >>> (@adoptopenjdk & @adoptajsr programs) >>>>> > >>> *Meet-a-Project - *MutabilityDetector >>>>> > >>> * | **Bitbucket >>>>> > >>> * * | **Github >>>>> > >>> * * | **LinkedIn >>>>> > >>> * >>>>> > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>>>> > >>> >>>>> > >>> *Don't chase success, rather aim for "Excellence", and success >>>>> will >>>>> > come >>>>> > >>> chasing after you!* >>>>> > >>> >>>>> > >> >>>>> > >> >>>>> > > >>>>> > > >>>>> > > -- >>>>> > > @theNeomatrix369 * | **Blog >>>>> > > ** | *LJC Associate & LJC >>>>> Advocate >>>>> > > (@adoptopenjdk & @adoptajsr programs) >>>>> > > *Meet-a-Project - *MutabilityDetector >>>>> > > * | **Bitbucket >>>>> > > * * | **Github >>>>> > > * * | **LinkedIn >>>>> > > * >>>>> > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>>>> > > >>>>> > > *Don't chase success, rather aim for "Excellence", and success >>>>> will come >>>>> > > chasing after you!* >>>>> > > >>>>> > >>>>> > >>>>> > -- >>>>> > Cheers, Martijn (Sent from Gmail Mobile) >>>>> > >>>>> >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dalibor.topic at oracle.com Wed Nov 4 13:58:44 2015 From: dalibor.topic at oracle.com (dalibor topic) Date: Wed, 4 Nov 2015 14:58:44 +0100 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: References: Message-ID: <563A0F14.9070205@oracle.com> On 30.10.2015 16:29, Vincent Privat wrote: > Hi, > - Is it expected to allow external people to have the possibility to > subscribe to JDK issues? See http://robilad.livejournal.com/139637.html cheers, dalibor topic -- Dalibor Topic | Principal Product Manager Phone: +494089091214 | Mobile: +491737185961 ORACLE Deutschland B.V. & Co. KG | K?hneh?fe 5 | 22761 Hamburg ORACLE Deutschland B.V. & Co. KG Hauptverwaltung: Riesstr. 25, D-80992 M?nchen Registergericht: Amtsgericht M?nchen, HRA 95603 Komplement?rin: ORACLE Deutschland Verwaltung B.V. Hertogswetering 163/167, 3543 AS Utrecht, Niederlande Handelsregister der Handelskammer Midden-Niederlande, Nr. 30143697 Gesch?ftsf?hrer: Alexander van der Ven, Astrid Kepper, Val Maher Oracle is committed to developing practices and products that help protect the environment From rory.odonnell at oracle.com Thu Nov 5 08:33:32 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Thu, 5 Nov 2015 08:33:32 +0000 Subject: JDK 9 early access b90 test results now available Message-ID: <563B145C.60901@oracle.com> * * JDK 9 ea b90 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 18 differences from the b88 test results. There are 3 testcase failures, these failures are under investigation. 0: /home/jtest/merge9/b88/jdk/JTwork pass: 5,243; fail: 25; error: 1; not run: 1,866 1: /home/jtest/merge9/b90/jdk/JTwork pass: 5,254; fail: 26; error: 2; not run: 1,871 0 1 Test fail pass java/io/BufferedInputStream/CloseStream.java --- pass java/io/ObjectInputStream/TestObjectStreamClass.java fail pass java/io/Serializable/unresolvableObjectStreamClass/UnresolvableObjectStreamClass.java --- pass java/lang/String/EqualsIgnoreCase.java pass fail java/net/InetAddress/IsReachableViaLoopbackTest.java --- fail java/net/InetAddress/getOriginalHostName.java pass error java/nio/Buffer/Basic.java --- pass java/sql/testng/test/sql/CallableStatementTests.java --- pass java/sql/testng/test/sql/PreparedStatementTests.java --- pass java/sql/testng/test/sql/StatementTests.java --- pass java/sql/testng/util/StubCallableStatement.java --- pass java/sql/testng/util/StubPreparedStatement.java --- pass java/sql/testng/util/StubStatement.java --- pass javax/imageio/plugins/bmp/Bug8066904.java --- pass sun/management/LazyCompositeDataTest.java pass fail sun/net/InetAddress/nameservice/dns/cname.sh --- pass sun/tools/jhsdb/BasicLauncherTest.java --- pass sun/tools/jstack/DeadlockDetectionTest.java 18 differences The hotspot test results contain 75 differences from the b88 test results. There is 1 testcase failure, this failure is under investigation. 0: /home/jtest/merge9/b88/hotspot/JTwork pass: 884; fail: 1; error: 3; not run: 35 1: /home/jtest/merge9/b90/hotspot/JTwork pass: 945; fail: 2; error: 4; not run: 44 0 1 Test pass --- compiler/TestMoveStoresOutOfLoopsStoreNoCtrl.java --- pass compiler/compilercontrol/matcher/MethodMatcherTest.java --- pass compiler/jvmci/JVM_GetJVMCIRuntimeTest.java --- pass compiler/jvmci/SecurityRestrictionsTest.java --- pass compiler/jvmci/compilerToVM/AllocateCompileIdTest.java --- pass compiler/jvmci/compilerToVM/CanInlineMethodTest.java --- pass compiler/jvmci/compilerToVM/CollectCountersTest.java --- pass compiler/jvmci/compilerToVM/DebugOutputTest.java --- pass compiler/jvmci/compilerToVM/DoNotInlineOrCompileTest.java --- pass compiler/jvmci/compilerToVM/ExecuteInstalledCodeTest.java --- pass compiler/jvmci/compilerToVM/FindUniqueConcreteMethodTest.java --- pass compiler/jvmci/compilerToVM/GetBytecodeTest.java --- pass compiler/jvmci/compilerToVM/GetClassInitializerTest.java --- pass compiler/jvmci/compilerToVM/GetConstantPoolTest.java --- pass compiler/jvmci/compilerToVM/GetExceptionTableTest.java --- pass compiler/jvmci/compilerToVM/GetImplementorTest.java --- pass compiler/jvmci/compilerToVM/GetLineNumberTableTest.java --- pass compiler/jvmci/compilerToVM/GetLocalVariableTableTest.java --- pass compiler/jvmci/compilerToVM/GetMaxCallTargetOffsetTest.java --- pass compiler/jvmci/compilerToVM/GetNextStackFrameTest.java --- pass compiler/jvmci/compilerToVM/GetResolvedJavaMethodAtSlotTest.java --- pass compiler/jvmci/compilerToVM/GetResolvedJavaMethodTest.java --- pass compiler/jvmci/compilerToVM/GetResolvedJavaTypeTest.java --- pass compiler/jvmci/compilerToVM/GetStackTraceElementTest.java --- pass compiler/jvmci/compilerToVM/GetSymbolTest.java --- pass compiler/jvmci/compilerToVM/GetVtableIndexForInterfaceTest.java --- pass compiler/jvmci/compilerToVM/HasCompiledCodeForOSRTest.java --- pass compiler/jvmci/compilerToVM/HasFinalizableSubclassTest.java --- pass compiler/jvmci/compilerToVM/InitializeConfigurationTest.java --- pass compiler/jvmci/compilerToVM/IsMatureTest.java --- pass compiler/jvmci/compilerToVM/JVM_RegisterJVMCINatives.java --- pass compiler/jvmci/compilerToVM/LookupKlassInPoolTest.java --- pass compiler/jvmci/compilerToVM/LookupTypeTest.java --- pass compiler/jvmci/compilerToVM/MethodIsIgnoredBySecurityStackWalkTest.java --- pass compiler/jvmci/compilerToVM/ReadUncompressedOopTest.java --- pass compiler/jvmci/compilerToVM/ReprofileTest.java --- pass compiler/jvmci/compilerToVM/ResolveConstantInPoolTest.java --- pass compiler/jvmci/compilerToVM/ResolveMethodTest.java --- pass compiler/jvmci/compilerToVM/ResolveTypeInPoolTest.java --- pass compiler/jvmci/compilerToVM/ShouldDebugNonSafepointsTest.java --- pass compiler/jvmci/compilerToVM/ShouldInlineMethodTest.java --- pass compiler/jvmci/events/JvmciCompleteInitializationTest.java --- pass compiler/jvmci/events/JvmciCreateMetaAccessContextTest.java --- pass compiler/jvmci/events/JvmciNotifyInstallEventTest.java --- pass compiler/jvmci/events/JvmciShutdownEventTest.java --- pass compiler/jvmci/jdk.vm.ci.options.test/src/jdk/vm/ci/options/test/NestedBooleanOptionValueTest.java --- pass compiler/jvmci/jdk.vm.ci.options.test/src/jdk/vm/ci/options/test/TestOptionValue.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/ConstantTest.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/RedefineClassTest.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/ResolvedJavaTypeResolveConcreteMethodTest.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/ResolvedJavaTypeResolveMethodTest.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestConstantReflectionProvider.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestJavaField.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestJavaMethod.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestJavaType.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestMetaAccessProvider.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaField.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaMethod.java --- pass compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaType.java --- pass compiler/loopopts/TestMoveStoresOutOfLoopsStoreNoCtrl.java --- pass compiler/oracle/MethodMatcherTest.java pass --- compiler/startup/SmallCodeCacheStartup.java --- pass gc/arguments/TestG1ConcMarkStepDurationMillis.java pass --- gc/arguments/TestInitialTenuringThreshold.java pass --- gc/arguments/TestObjectTenuringFlags.java --- pass gc/cms/TestCMSScavengeBeforeRemark.java --- pass gc/logging/TestPrintReferences.java pass --- runtime/6888954/vmerrors.sh --- pass runtime/CommandLine/VMOptionsFile/TestVMOptionsFile.java --- pass runtime/ErrorHandling/ErrorHandler.java pass error runtime/Thread/Fibonacci.java --- pass runtime/classFileParserBug/InitInInterface.java --- pass serviceability/logging/TestBasicLogOutput.java --- pass serviceability/sa/DeadlockDetectionTest.java pass fail serviceability/threads/TestFalseDeadLock.java 75 differences The langtools test results contain 5 differences from the b88 test results. No new testcase failures found. 0: /home/jtest/merge9/b88/langtools/JTwork pass: 3,290; not run: 16 1: /home/jtest/merge9/b90/langtools/jtreg/JTwork pass: 3,295; not run: 50 0 1 Test --- pass tools/javac/NameClash/NameClashTest.java --- pass tools/javac/annotations/typeAnnotations/newlocations/AllLocations.java --- pass tools/javac/doctree/InPreTest.java --- pass tools/javac/lambda/MethodReference74.java --- pass tools/javac/linenumbers/FinallyLineNumberTest.java 5 differences The nashorn test result is available at _http://download.java.net/openjdk/testresults/9/archives/b90/emailable-report.html_ -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Fri Nov 6 23:30:43 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Fri, 6 Nov 2015 23:30:43 +0000 Subject: Build failed in Jenkins: TestNG #57 In-Reply-To: References: <545310728.21.1446268072141.JavaMail.adopt-openjdk@jenkins-adopt-openjdk> <716780633.22.1446289385091.JavaMail.adopt-openjdk@jenkins-adopt-openjdk> Message-ID: TestNG now builds on both JDK9 and JDK9 Jigsaw, see https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG/ https://adopt-openjdk.ci.cloudbees.com/view/Quality%20Outreach/job/TestNG-Jigsaw/ Cheers, Mani On Sat, Oct 31, 2015 at 11:10 AM, Mani Sarkar wrote: > FYI TestNG fails with latest JDK9 Build 88 ( > https://jdk9.java.net/download/) > > The authors should have already been notified, but I'll also send them a > ping. > > Cheers, > Mani > > ---------- Forwarded message ---------- > From: > Date: Sat, Oct 31, 2015 at 11:03 AM > Subject: Build failed in Jenkins: TestNG #57 > To: martijnverburg at gmail.com, sadhak001 at gmail.com > > > See > > ------------------------------------------ > [...truncated 2578 lines...] > Note: Recompile with -Xlint:unchecked for details. > 1 warning > > :processResources > :classes > :jar > :javadoc< > https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/src/main/java/org/testng/TestNG.java>:35: > error: cannot find symbol > import org.testng.internal.Version; > ^ > symbol: class Version > location: package org.testng.internal > > 1 warning > :javadocJar > :sourcesJar > :signArchives SKIPPED > :assemble > :compileTestJavawarning: [options] bootstrap class path not set in > conjunction with -source 1.7 > Note: Some input files use or override a deprecated API. > Note: Recompile with -Xlint:deprecation for details. > Note: Some input files use unchecked or unsafe operations. > Note: Recompile with -Xlint:unchecked for details. > 1 warning > > :processTestResources > :testClasses > :test > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > test.groupinvocation.GroupSuiteTest.Regression2 > FAILED > java.lang.AssertionError at GroupSuiteTest.java:69 > > TestNG > Regression2 > > test.annotationtransformer.AnnotationTransformerTest.Regression2 FAILED > java.lang.AssertionError at AnnotationTransformerTest.java:46 > > TestNG > Regression2 > > test.annotationtransformer.AnnotationTransformerTest.Regression2 FAILED > java.lang.AssertionError at AnnotationTransformerTest.java:75 > > TestNG > Regression2 > test.preserveorder.PreserveOrderTest.Regression2 > FAILED > java.lang.AssertionError at PreserveOrderTest.java:105 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > test.methodselectors.CommandLineTest.Method > selectors FAILED > java.lang.AssertionError at CommandLineTest.java:176 > > TestNG > Method selectors > > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED > java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 > > TestNG > Method selectors > > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED > java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 > > TestNG > Method selectors > > test.methodselectors.MethodSelectorInSuiteTest.Method selectors FAILED > java.lang.AssertionError at MethodSelectorInSuiteTest.java:75 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:36 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:50 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:112 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:97 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:134 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:79 > > TestNG > JUnit > test.JUnitTest1.JUnit FAILED > java.lang.AssertionError at JUnitTest1.java:65 > > TestNG > JUnit > test.CommandLineTest.JUnit FAILED > java.lang.AssertionError at CommandLineTest.java:35 > > TestNG > JUnit > test.CommandLineTest.JUnit FAILED > java.lang.AssertionError at CommandLineTest.java:125 > > TestNG > JUnit > test.JUnit4Test.JUnit FAILED > java.lang.AssertionError at JUnit4Test.java:46 > > TestNG > JUnit > test.JUnit4Test.JUnit FAILED > java.lang.AssertionError at JUnit4Test.java:61 > > TestNG > JUnit > test.JUnit4Test.JUnit FAILED > java.lang.AssertionError at JUnit4Test.java:77 > > TestNG > JUnit > test.JUnit4Test.JUnit FAILED > java.lang.AssertionError at JUnit4Test.java:92 > > TestNG > JUnit > test.JUnit4Test.JUnit FAILED > java.lang.AssertionError at JUnit4Test.java:31 > > TestNG > RetryAnalyzer > > test.retryAnalyzer.RetryAnalyzerTest.RetryAnalyzer FAILED > java.lang.AssertionError at RetryAnalyzerTest.java:25 > > TestNG > MethodInterceptor > > test.methodinterceptors.multipleinterceptors.MultipleInterceptorsTest.MethodInterceptor > FAILED > java.lang.AssertionError at MultipleInterceptorsTest.java:24 > > TestNG > Bug173 > test.testng173.TestNG173Test.Bug173 FAILED > java.lang.AssertionError at TestNG173Test.java:39 > > TestNG > Bug173 > test.testng173.TestNG173Test.Bug173 FAILED > java.lang.AssertionError at TestNG173Test.java:62 > > TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED > java.lang.AssertionError at MixedTest.java:44 > > TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED > java.lang.AssertionError at MixedTest.java:59 > > TestNG > Mixed > test.mixed.MixedTest.Mixed FAILED > java.lang.AssertionError at MixedTest.java:28 > > 1160 tests completed, 42 failed > :test FAILED > > FAILURE: Build failed with an exception. > > * What went wrong: > Execution failed for task ':test'. > > There were failing tests. See the report at: file://< > https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/build/reports/tests/index.html > > > > * Try: > Run with --info or --debug option to get more log output. > > * Exception is: > org.gradle.api.tasks.TaskExecutionException: Execution failed for task > ':test'. > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46) > at > org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35) > at > org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64) > at > org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) > at > org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) > at > org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53) > at > org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:208) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:186) > at > org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:62) > at > org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:50) > at > org.gradle.execution.taskgraph.DefaultTaskPlanExecutor.process(DefaultTaskPlanExecutor.java:25) > at > org.gradle.execution.taskgraph.DefaultTaskGraphExecuter.execute(DefaultTaskGraphExecuter.java:111) > at > org.gradle.execution.SelectedTaskExecutionAction.execute(SelectedTaskExecutionAction.java:37) > at > org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62) > at > org.gradle.execution.DefaultBuildExecuter.access$200(DefaultBuildExecuter.java:23) > at > org.gradle.execution.DefaultBuildExecuter$2.proceed(DefaultBuildExecuter.java:68) > at > org.gradle.execution.DryRunBuildExecutionAction.execute(DryRunBuildExecutionAction.java:32) > at > org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:62) > at > org.gradle.execution.DefaultBuildExecuter.execute(DefaultBuildExecuter.java:55) > at > org.gradle.initialization.DefaultGradleLauncher$6.run(DefaultGradleLauncher.java:174) > at org.gradle.internal.Factories$1.create(Factories.java:22) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:47) > at > org.gradle.initialization.DefaultGradleLauncher.runBuildOperation(DefaultGradleLauncher.java:189) > at > org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:171) > at > org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:35) > at > org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:104) > at > org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:97) > at > org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:62) > at > org.gradle.initialization.DefaultGradleLauncher.runRootBuildOperation(DefaultGradleLauncher.java:184) > at > org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:97) > at > org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:86) > at > org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:93) > at > org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28) > at > org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35) > at > org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:43) > at > org.gradle.launcher.exec.InProcessBuildActionExecuter.execute(InProcessBuildActionExecuter.java:27) > at > org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:72) > at > org.gradle.launcher.exec.ContinuousBuildActionExecuter.execute(ContinuousBuildActionExecuter.java:44) > at > org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:50) > at > org.gradle.launcher.exec.DaemonUsageSuggestingBuildActionExecuter.execute(DaemonUsageSuggestingBuildActionExecuter.java:27) > at > org.gradle.launcher.cli.RunBuildAction.run(RunBuildAction.java:40) > at > org.gradle.internal.Actions$RunnableActionAdapter.execute(Actions.java:170) > at > org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:237) > at > org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:210) > at > org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:35) > at > org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24) > at > org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:206) > at > org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:169) > at > org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33) > at > org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22) > at org.gradle.launcher.Main.doAction(Main.java:33) > at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45) > at > org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:54) > at > org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:35) > at org.gradle.launcher.GradleMain.main(GradleMain.java:23) > at > org.gradle.wrapper.BootstrapMainStarter.start(BootstrapMainStarter.java:30) > at > org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:127) > at > org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61) > Caused by: org.gradle.api.GradleException: There were failing tests. See > the report at: file://< > https://adopt-openjdk.ci.cloudbees.com/job/TestNG/ws/build/reports/tests/index.html > > > at > org.gradle.api.tasks.testing.Test.handleTestFailures(Test.java:1129) > at org.gradle.api.tasks.testing.Test.executeTests(Test.java:567) > at > org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75) > at > org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:226) > at > org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:219) > at > org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:208) > at > org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:585) > at > org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:568) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80) > at > org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61) > ... 61 more > > > BUILD FAILED > > Total time: 2 mins 27.355 secs > Build step 'Execute shell' marked build as failure > Archiving artifacts > > > > -- > @theNeomatrix369 * | **Blog > ** | *LJC Associate & LJC Advocate > (@adoptopenjdk & @adoptajsr programs) > *Meet-a-Project - *MutabilityDetector > * | **Bitbucket > * * | **Github > * * | **LinkedIn > * > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > > *Don't chase success, rather aim for "Excellence", and success will come > chasing after you!* > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From weijun.wang at oracle.com Wed Nov 11 02:20:43 2015 From: weijun.wang at oracle.com (Wang Weijun) Date: Wed, 11 Nov 2015 10:20:43 +0800 Subject: JOSM feedback on Java 7,8,9, including Jigsaw EA In-Reply-To: <31098CBD-716A-4D4A-ABAF-48EBBEEE97AB@oracle.com> References: <31098CBD-716A-4D4A-ABAF-48EBBEEE97AB@oracle.com> Message-ID: <50AC8E9B-0FE1-484C-92EA-DF78514360E4@oracle.com> Ping again. Will the future JRE only include java.se? In other words, what will the java.com download for non-developers contain? Thanks Max > On Nov 5, 2015, at 10:07 AM, Wang Weijun wrote: > > I was talking with Vincent off the list, but it seems better to be back. > > Here is Vincent's mail on how he thinks of the new API we are about to provide in JDK-8058778. > >> The new API is interesting but if it's not available in Java SE I'm afraid it does not fit our use case. We cannot make JOSM depend on a JDK at runtime just for this feature :( > > There might be some confusion on what "JDK" means. It used to be the developer's toolkit versus JRE the runtime, but as for module names, a jdk.* module contains APIs defined by OpenJDK instead of Java SE. In fact, most of them are not especially designed for developers. > > That said, I am not exactly sure what kind of images we will release after jigsaw. If there is still a JRE, I think it will include not only the java.* modules but also some jdk.* ones. I hope jdk.security.cert is one of them. > > Personally I am not afraid of using jdk.* modules, since almost every JDK distribution is based on OpenJDK. At least it is now a supported API of OpenJDK instead of old sun.* classes that were never claimed to be supported by anyone. > > In fact, keytool was not defined in Java SE either. It was in JRE though. > > Thanks > Max From abdul.kolarkunnu at oracle.com Wed Nov 11 17:16:16 2015 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Wed, 11 Nov 2015 09:16:16 -0800 (PST) Subject: JDK 9 b91 test results now available Message-ID: JDK 9 ea b91 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 3 differences from the b90 test results. No new testcase failures found. 0: /home/jtest/merge9/b90/jdk/JTwork pass: 5,254; fail: 26; error: 2; not run: 1,871 1: /home/jtest/merge9/b91/jdk/JTwork pass: 5,257; fail: 23; error: 2; not run: 1,871 0 1 Test fail pass java/net/InetAddress/IsReachableViaLoopbackTest.java fail pass java/net/InetAddress/getOriginalHostName.java fail pass sun/net/InetAddress/nameservice/dns/cname.sh 3 differences The hotspot test results contain 3 differences from the b90 test results. No new testcase failures found. 0: /home/jtest/merge9/b90/hotspot/JTwork pass: 945; fail: 2; error: 4; not run: 44 1: /home/jtest/merge9/b91/hotspot/JTwork pass: 948; error: 3; not run: 44 0 1 Test fail pass gc/TestNUMAPageSize.java error pass runtime/Thread/Fibonacci.java fail pass serviceability/threads/TestFalseDeadLock.java 3 differences The langtools test results contain 1 difference from the b90 test results. No new testcase failures found. 0: /home/jtest/merge9/b90/langtools/jtreg/JTwork pass: 3,295; not run: 50 1: /home/jtest/merge9/b91/langtools/JTwork pass: 3,296; not run: 50 0 1 Test --- pass tools/javac/doctree/dcapi/DocCommentTreeApiTester.java 1 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/b91/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Tue Nov 17 00:34:25 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Tue, 17 Nov 2015 00:34:25 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Hi all, Martijn, The gitbook has now been transfered to the adoptopenjdk organisation, the new location is https://www.gitbook.com/book/adoptopenjdk/adoptopenjdk-getting-started-kit/details, the providers of gitbook have made forwarding arrangements, any old links will get redirected to the new location. Also with that I have also moved the adopt-openjdk-kiss-vagrant to the adoptopenjdk organisation (see https://github.com/AdoptOpenJDK/adopt-openjdk-kiss-vagrant). Please give it a whirl and get back to us if you have spotted any issues. Cheers, Mani On Wed, Nov 4, 2015 at 11:46 AM, Martijn Verburg wrote: > Hi Mohan, > > That is good advice yes - the IRC channel for the JSRs (different > programme) hasn't really worked. The IRC channel for the official openjdk > is actually quite active. > > Cheers, > Martijn > > On 4 November 2015 at 11:35, Mohan Radhakrishnan < > radhakrishnan.mohan at gmail.com> wrote: > > > If you're interested in a particular area but don't have any specific > >> ideas about what to do then feel free to post a query to the appropriate > >> Group or Projectdevelopment list to ask > >> for suggestions that match your skills and knowledge. A list of all the > >> Groups and Projects > >> may be found at the left-hand > >> side of this page; you are more than welcome to subscribe > >> to any of their mailing lists. A > >> complete list of all of the Groups, Projects, people and their roles > may be > >> found in the census . > > > > > > This is the best advice in http://openjdk.java.net/contribute/. > > One could regularly participate in the IRC discussion of JSR;s. I tried > > that. But even then generally the close-knit group may meet at > conferences > > that all cannot pay to attend. > > > > Thanks, > > Mohan > > > > On 3 November 2015 at 20:49, Martijn Verburg > > wrote: > > > >> Yes, it pays to discuss the change *before* you submit it, you'd be > >> surprised why certain things are the way they are :-) > >> > >> Cheers, > >> Martijn > >> > >> On 3 November 2015 at 12:02, Mohan Radhakrishnan < > >> radhakrishnan.mohan at gmail.com> wrote: > >> > >>> That is interesting. They do accept such small changes then. > >>> > >>> Thanks, > >>> Mohan > >>> > >>> On 3 November 2015 at 15:01, Martijn Verburg > > >>> wrote: > >>> > >>>> I think there should also be clear guidance on how to submit your > first > >>>> patch for a small, low-impact change (like a code clean up). Over > time we > >>>> want more people to gain Author+ status in the various projects, > especially > >>>> around safer parts of OpenJDK (e.g. Not Hotspot) > >>>> > >>>> Cheers, > >>>> Martijn > >>>> > >>>> On 3 November 2015 at 06:07, Mohan Radhakrishnan < > >>>> radhakrishnan.mohan at gmail.com> wrote: > >>>> > >>>>> I read the contribution procedure. > >>>>> > >>>>> Are these basically the avenues ? > >>>>> > >>>>> 1. One could individually participate in JCP spec. activities without > >>>>> guidance depending on one's skill level. > >>>>> 2. Participate along with the local JUG. > >>>>> 3. Contribute to one of the OpenJDK projects like JITWatch etc. > >>>>> 4. Contribute to documentation. > >>>>> > >>>>> Thanks, > >>>>> Mohan > >>>>> > >>>>> On 3 November 2015 at 06:09, Martijn Verburg < > martijnverburg at gmail.com > >>>>> > > >>>>> wrote: > >>>>> > >>>>> > Once you make the move it'll get more eyes and more PRs will start > to > >>>>> > arrive (much like Jitwatch and jcountdown I suspect). > >>>>> > > >>>>> > Is there someone in this list who is fairly new and will go through > >>>>> Mani's > >>>>> > doc? > >>>>> > > >>>>> > Cheers, > >>>>> > Martijn > >>>>> > > >>>>> > On Monday, 2 November 2015, Mani Sarkar > wrote: > >>>>> > > >>>>> > > Martijn, > >>>>> > > > >>>>> > > I'm in conversation with the guys about moving it, and after > >>>>> Devoxx BE is > >>>>> > > a better move I think although I would have liked it to be > earlier. > >>>>> > > > >>>>> > > On a more important note, I was wondering if the contents of the > >>>>> pages I > >>>>> > > shared were good, if not, happy to change them so that adoptors > >>>>> get the > >>>>> > > right info. > >>>>> > > > >>>>> > > Cheers, > >>>>> > > Mani > >>>>> > > > >>>>> > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < > >>>>> > martijnverburg at gmail.com > >>>>> > > > > wrote: > >>>>> > > > >>>>> > >> Hey Mani, > >>>>> > >> > >>>>> > >> Ah, I wondered where that was being hosted. You're happy to > move > >>>>> that > >>>>> > to > >>>>> > >> the AdoptOpenJDK repo post Devoxx correct? I've added a link to > >>>>> this > >>>>> > Kit > >>>>> > >> in the wiki and have also added the OpenJDK IRC channel link to > >>>>> the > >>>>> > wiki as > >>>>> > >> well. > >>>>> > >> > >>>>> > >> Cheers, > >>>>> > >> Martijn > >>>>> > >> > >>>>> > >> On 31 October 2015 at 09:34, Mani Sarkar >>>>> > >> > wrote: > >>>>> > >> > >>>>> > >>> Hi all, > >>>>> > >>> > >>>>> > >>> I have put together this page on how to ... > >>>>> > >>> > >>>>> > >>> > >>>>> > >>> > >>>>> > > >>>>> > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html > >>>>> > >>> > >>>>> > >>> As a community we should feel free to amend the contents as per > >>>>> what > >>>>> > >>> really is meant by contributions. > >>>>> > >>> > >>>>> > >>> Anything incorrect or missing - feel free to report here or > >>>>> create a > >>>>> > >>> pull request (see > >>>>> > >>> > >>>>> > > >>>>> > https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html > >>>>> > >>> ). > >>>>> > >>> > >>>>> > >>> Thanks for reading and contributing. > >>>>> > >>> > >>>>> > >>> Cheers, > >>>>> > >>> Mani > >>>>> > >>> > >>>>> > >>> -- > >>>>> > >>> @theNeomatrix369 * | > >>>>> **Blog > >>>>> > >>> ** | *LJC Associate & LJC > >>>>> > Advocate > >>>>> > >>> (@adoptopenjdk & @adoptajsr programs) > >>>>> > >>> *Meet-a-Project - *MutabilityDetector > >>>>> > >>> * | **Bitbucket > >>>>> > >>> * * | **Github > >>>>> > >>> * * | **LinkedIn > >>>>> > >>> * > >>>>> > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > >>>>> > >>> > >>>>> > >>> *Don't chase success, rather aim for "Excellence", and success > >>>>> will > >>>>> > come > >>>>> > >>> chasing after you!* > >>>>> > >>> > >>>>> > >> > >>>>> > >> > >>>>> > > > >>>>> > > > >>>>> > > -- > >>>>> > > @theNeomatrix369 * | > **Blog > >>>>> > > ** | *LJC Associate & LJC > >>>>> Advocate > >>>>> > > (@adoptopenjdk & @adoptajsr programs) > >>>>> > > *Meet-a-Project - *MutabilityDetector > >>>>> > > * | **Bitbucket > >>>>> > > * * | **Github > >>>>> > > * * | **LinkedIn > >>>>> > > * > >>>>> > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ > >>>>> > > > >>>>> > > *Don't chase success, rather aim for "Excellence", and success > >>>>> will come > >>>>> > > chasing after you!* > >>>>> > > > >>>>> > > >>>>> > > >>>>> > -- > >>>>> > Cheers, Martijn (Sent from Gmail Mobile) > >>>>> > > >>>>> > >>>> > >>>> > >>> > >> > > > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Tue Nov 17 09:38:00 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 17 Nov 2015 09:38:00 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Mani, John, Fantastic work! Thank you so much for porting this across. I did get 404's following the first two links though? https://adoptopenjdk.gitbooks.io/adoptopenjdk-getting-started-kit/content/how-to-navigate/how-to-navigate-and-make-progress.html https://adoptopenjdk.gitbooks.io/adoptopenjdk-getting-started-kit/content/adopt-openjdk-getting-started/adopt_openjdk_-_getting_started.html Cheers, Martijn On 17 November 2015 at 01:02, John Patrick wrote: > Hi all and Mani, > > I've just done created pull request based on feedback and experience at > hack the tower at the weekend. > > For those interested in the vagrant vm details, along with what I > changed/fixed and why please check out the pull request; > https://github.com/AdoptOpenJDK/adopt-openjdk-kiss-vagrant/pull/3 > > Still looking at created the common IDE projects so importing into the > users native IDE is simpler. > > Cheers, > John > > > On 17 November 2015 at 00:34, Mani Sarkar wrote: > >> Hi all, Martijn, >> >> The gitbook has now been transfered to the adoptopenjdk organisation, the >> new location is >> >> https://www.gitbook.com/book/adoptopenjdk/adoptopenjdk-getting-started-kit/details >> , >> the providers of gitbook have made forwarding arrangements, any old links >> will get redirected to the new location. >> >> Also with that I have also moved the adopt-openjdk-kiss-vagrant to the >> adoptopenjdk organisation (see >> https://github.com/AdoptOpenJDK/adopt-openjdk-kiss-vagrant). >> >> Please give it a whirl and get back to us if you have spotted any issues. >> >> Cheers, >> Mani >> >> On Wed, Nov 4, 2015 at 11:46 AM, Martijn Verburg < >> martijnverburg at gmail.com> >> wrote: >> >> > Hi Mohan, >> > >> > That is good advice yes - the IRC channel for the JSRs (different >> > programme) hasn't really worked. The IRC channel for the official >> openjdk >> > is actually quite active. >> > >> > Cheers, >> > Martijn >> > >> > On 4 November 2015 at 11:35, Mohan Radhakrishnan < >> > radhakrishnan.mohan at gmail.com> wrote: >> > >> > > If you're interested in a particular area but don't have any specific >> > >> ideas about what to do then feel free to post a query to the >> appropriate >> > >> Group or Projectdevelopment list to >> ask >> > >> for suggestions that match your skills and knowledge. A list of all >> the >> > >> Groups and Projects >> > >> may be found at the >> left-hand >> > >> side of this page; you are more than welcome to subscribe >> > >> to any of their mailing lists. A >> > >> complete list of all of the Groups, Projects, people and their roles >> > may be >> > >> found in the census . >> > > >> > > >> > > This is the best advice in http://openjdk.java.net/contribute/. >> > > One could regularly participate in the IRC discussion of JSR;s. I >> tried >> > > that. But even then generally the close-knit group may meet at >> > conferences >> > > that all cannot pay to attend. >> > > >> > > Thanks, >> > > Mohan >> > > >> > > On 3 November 2015 at 20:49, Martijn Verburg < >> martijnverburg at gmail.com> >> > > wrote: >> > > >> > >> Yes, it pays to discuss the change *before* you submit it, you'd be >> > >> surprised why certain things are the way they are :-) >> > >> >> > >> Cheers, >> > >> Martijn >> > >> >> > >> On 3 November 2015 at 12:02, Mohan Radhakrishnan < >> > >> radhakrishnan.mohan at gmail.com> wrote: >> > >> >> > >>> That is interesting. They do accept such small changes then. >> > >>> >> > >>> Thanks, >> > >>> Mohan >> > >>> >> > >>> On 3 November 2015 at 15:01, Martijn Verburg < >> martijnverburg at gmail.com >> > > >> > >>> wrote: >> > >>> >> > >>>> I think there should also be clear guidance on how to submit your >> > first >> > >>>> patch for a small, low-impact change (like a code clean up). Over >> > time we >> > >>>> want more people to gain Author+ status in the various projects, >> > especially >> > >>>> around safer parts of OpenJDK (e.g. Not Hotspot) >> > >>>> >> > >>>> Cheers, >> > >>>> Martijn >> > >>>> >> > >>>> On 3 November 2015 at 06:07, Mohan Radhakrishnan < >> > >>>> radhakrishnan.mohan at gmail.com> wrote: >> > >>>> >> > >>>>> I read the contribution procedure. >> > >>>>> >> > >>>>> Are these basically the avenues ? >> > >>>>> >> > >>>>> 1. One could individually participate in JCP spec. activities >> without >> > >>>>> guidance depending on one's skill level. >> > >>>>> 2. Participate along with the local JUG. >> > >>>>> 3. Contribute to one of the OpenJDK projects like JITWatch etc. >> > >>>>> 4. Contribute to documentation. >> > >>>>> >> > >>>>> Thanks, >> > >>>>> Mohan >> > >>>>> >> > >>>>> On 3 November 2015 at 06:09, Martijn Verburg < >> > martijnverburg at gmail.com >> > >>>>> > >> > >>>>> wrote: >> > >>>>> >> > >>>>> > Once you make the move it'll get more eyes and more PRs will >> start >> > to >> > >>>>> > arrive (much like Jitwatch and jcountdown I suspect). >> > >>>>> > >> > >>>>> > Is there someone in this list who is fairly new and will go >> through >> > >>>>> Mani's >> > >>>>> > doc? >> > >>>>> > >> > >>>>> > Cheers, >> > >>>>> > Martijn >> > >>>>> > >> > >>>>> > On Monday, 2 November 2015, Mani Sarkar >> > wrote: >> > >>>>> > >> > >>>>> > > Martijn, >> > >>>>> > > >> > >>>>> > > I'm in conversation with the guys about moving it, and after >> > >>>>> Devoxx BE is >> > >>>>> > > a better move I think although I would have liked it to be >> > earlier. >> > >>>>> > > >> > >>>>> > > On a more important note, I was wondering if the contents of >> the >> > >>>>> pages I >> > >>>>> > > shared were good, if not, happy to change them so that >> adoptors >> > >>>>> get the >> > >>>>> > > right info. >> > >>>>> > > >> > >>>>> > > Cheers, >> > >>>>> > > Mani >> > >>>>> > > >> > >>>>> > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < >> > >>>>> > martijnverburg at gmail.com >> > >>>>> > > > >> > wrote: >> > >>>>> > > >> > >>>>> > >> Hey Mani, >> > >>>>> > >> >> > >>>>> > >> Ah, I wondered where that was being hosted. You're happy to >> > move >> > >>>>> that >> > >>>>> > to >> > >>>>> > >> the AdoptOpenJDK repo post Devoxx correct? I've added a >> link to >> > >>>>> this >> > >>>>> > Kit >> > >>>>> > >> in the wiki and have also added the OpenJDK IRC channel link >> to >> > >>>>> the >> > >>>>> > wiki as >> > >>>>> > >> well. >> > >>>>> > >> >> > >>>>> > >> Cheers, >> > >>>>> > >> Martijn >> > >>>>> > >> >> > >>>>> > >> On 31 October 2015 at 09:34, Mani Sarkar < >> sadhak001 at gmail.com >> > >>>>> > >> > >> wrote: >> > >>>>> > >> >> > >>>>> > >>> Hi all, >> > >>>>> > >>> >> > >>>>> > >>> I have put together this page on how to ... >> > >>>>> > >>> >> > >>>>> > >>> >> > >>>>> > >>> >> > >>>>> > >> > >>>>> >> > >> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >> > >>>>> > >>> >> > >>>>> > >>> As a community we should feel free to amend the contents as >> per >> > >>>>> what >> > >>>>> > >>> really is meant by contributions. >> > >>>>> > >>> >> > >>>>> > >>> Anything incorrect or missing - feel free to report here or >> > >>>>> create a >> > >>>>> > >>> pull request (see >> > >>>>> > >>> >> > >>>>> > >> > >>>>> >> > >> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >> > >>>>> > >>> ). >> > >>>>> > >>> >> > >>>>> > >>> Thanks for reading and contributing. >> > >>>>> > >>> >> > >>>>> > >>> Cheers, >> > >>>>> > >>> Mani >> > >>>>> > >>> >> > >>>>> > >>> -- >> > >>>>> > >>> @theNeomatrix369 * | >> > >>>>> **Blog >> > >>>>> > >>> ** | *LJC Associate & >> LJC >> > >>>>> > Advocate >> > >>>>> > >>> (@adoptopenjdk & @adoptajsr programs) >> > >>>>> > >>> *Meet-a-Project - *MutabilityDetector >> > >>>>> > >>> * | **Bitbucket >> > >>>>> > >>> * * | **Github >> > >>>>> > >>> * * | **LinkedIn >> > >>>>> > >>> * >> > >>>>> > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >> > >>>>> > >>> >> > >>>>> > >>> *Don't chase success, rather aim for "Excellence", and >> success >> > >>>>> will >> > >>>>> > come >> > >>>>> > >>> chasing after you!* >> > >>>>> > >>> >> > >>>>> > >> >> > >>>>> > >> >> > >>>>> > > >> > >>>>> > > >> > >>>>> > > -- >> > >>>>> > > @theNeomatrix369 * | >> > **Blog >> > >>>>> > > ** | *LJC Associate & >> LJC >> > >>>>> Advocate >> > >>>>> > > (@adoptopenjdk & @adoptajsr programs) >> > >>>>> > > *Meet-a-Project - *MutabilityDetector >> > >>>>> > > * | **Bitbucket >> > >>>>> > > * * | **Github >> > >>>>> > > * * | **LinkedIn >> > >>>>> > > * >> > >>>>> > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >> > >>>>> > > >> > >>>>> > > *Don't chase success, rather aim for "Excellence", and success >> > >>>>> will come >> > >>>>> > > chasing after you!* >> > >>>>> > > >> > >>>>> > >> > >>>>> > >> > >>>>> > -- >> > >>>>> > Cheers, Martijn (Sent from Gmail Mobile) >> > >>>>> > >> > >>>>> >> > >>>> >> > >>>> >> > >>> >> > >> >> > > >> > >> >> >> >> -- >> @theNeomatrix369 * | **Blog >> ** | *LJC Associate & LJC Advocate >> (@adoptopenjdk & @adoptajsr programs) >> *Meet-a-Project - *MutabilityDetector >> * | **Bitbucket >> * * | **Github >> * * | **LinkedIn >> * >> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >> >> *Don't chase success, rather aim for "Excellence", and success will come >> chasing after you!* >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Tue Nov 17 10:33:01 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Tue, 17 Nov 2015 10:33:01 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Also, I forgot where we go to in terms of hosting some of these pre built VMs with the environments all set up. Have you tried using GitHubs large file service? If not we can perhaps go back to using Bintray. Cheers, Martijn On 17 November 2015 at 09:38, Martijn Verburg wrote: > Mani, John, > > Fantastic work! Thank you so much for porting this across. I did get > 404's following the first two links though? > > > https://adoptopenjdk.gitbooks.io/adoptopenjdk-getting-started-kit/content/how-to-navigate/how-to-navigate-and-make-progress.html > > https://adoptopenjdk.gitbooks.io/adoptopenjdk-getting-started-kit/content/adopt-openjdk-getting-started/adopt_openjdk_-_getting_started.html > > > Cheers, > Martijn > > On 17 November 2015 at 01:02, John Patrick wrote: > >> Hi all and Mani, >> >> I've just done created pull request based on feedback and experience at >> hack the tower at the weekend. >> >> For those interested in the vagrant vm details, along with what I >> changed/fixed and why please check out the pull request; >> https://github.com/AdoptOpenJDK/adopt-openjdk-kiss-vagrant/pull/3 >> >> Still looking at created the common IDE projects so importing into the >> users native IDE is simpler. >> >> Cheers, >> John >> >> >> On 17 November 2015 at 00:34, Mani Sarkar wrote: >> >>> Hi all, Martijn, >>> >>> The gitbook has now been transfered to the adoptopenjdk organisation, the >>> new location is >>> >>> https://www.gitbook.com/book/adoptopenjdk/adoptopenjdk-getting-started-kit/details >>> , >>> the providers of gitbook have made forwarding arrangements, any old links >>> will get redirected to the new location. >>> >>> Also with that I have also moved the adopt-openjdk-kiss-vagrant to the >>> adoptopenjdk organisation (see >>> https://github.com/AdoptOpenJDK/adopt-openjdk-kiss-vagrant). >>> >>> Please give it a whirl and get back to us if you have spotted any issues. >>> >>> Cheers, >>> Mani >>> >>> On Wed, Nov 4, 2015 at 11:46 AM, Martijn Verburg < >>> martijnverburg at gmail.com> >>> wrote: >>> >>> > Hi Mohan, >>> > >>> > That is good advice yes - the IRC channel for the JSRs (different >>> > programme) hasn't really worked. The IRC channel for the official >>> openjdk >>> > is actually quite active. >>> > >>> > Cheers, >>> > Martijn >>> > >>> > On 4 November 2015 at 11:35, Mohan Radhakrishnan < >>> > radhakrishnan.mohan at gmail.com> wrote: >>> > >>> > > If you're interested in a particular area but don't have any specific >>> > >> ideas about what to do then feel free to post a query to the >>> appropriate >>> > >> Group or Projectdevelopment list >>> to ask >>> > >> for suggestions that match your skills and knowledge. A list of all >>> the >>> > >> Groups and Projects >>> > >> may be found at the >>> left-hand >>> > >> side of this page; you are more than welcome to subscribe >>> > >> to any of their mailing lists. A >>> > >> complete list of all of the Groups, Projects, people and their roles >>> > may be >>> > >> found in the census . >>> > > >>> > > >>> > > This is the best advice in http://openjdk.java.net/contribute/. >>> > > One could regularly participate in the IRC discussion of JSR;s. I >>> tried >>> > > that. But even then generally the close-knit group may meet at >>> > conferences >>> > > that all cannot pay to attend. >>> > > >>> > > Thanks, >>> > > Mohan >>> > > >>> > > On 3 November 2015 at 20:49, Martijn Verburg < >>> martijnverburg at gmail.com> >>> > > wrote: >>> > > >>> > >> Yes, it pays to discuss the change *before* you submit it, you'd be >>> > >> surprised why certain things are the way they are :-) >>> > >> >>> > >> Cheers, >>> > >> Martijn >>> > >> >>> > >> On 3 November 2015 at 12:02, Mohan Radhakrishnan < >>> > >> radhakrishnan.mohan at gmail.com> wrote: >>> > >> >>> > >>> That is interesting. They do accept such small changes then. >>> > >>> >>> > >>> Thanks, >>> > >>> Mohan >>> > >>> >>> > >>> On 3 November 2015 at 15:01, Martijn Verburg < >>> martijnverburg at gmail.com >>> > > >>> > >>> wrote: >>> > >>> >>> > >>>> I think there should also be clear guidance on how to submit your >>> > first >>> > >>>> patch for a small, low-impact change (like a code clean up). Over >>> > time we >>> > >>>> want more people to gain Author+ status in the various projects, >>> > especially >>> > >>>> around safer parts of OpenJDK (e.g. Not Hotspot) >>> > >>>> >>> > >>>> Cheers, >>> > >>>> Martijn >>> > >>>> >>> > >>>> On 3 November 2015 at 06:07, Mohan Radhakrishnan < >>> > >>>> radhakrishnan.mohan at gmail.com> wrote: >>> > >>>> >>> > >>>>> I read the contribution procedure. >>> > >>>>> >>> > >>>>> Are these basically the avenues ? >>> > >>>>> >>> > >>>>> 1. One could individually participate in JCP spec. activities >>> without >>> > >>>>> guidance depending on one's skill level. >>> > >>>>> 2. Participate along with the local JUG. >>> > >>>>> 3. Contribute to one of the OpenJDK projects like JITWatch etc. >>> > >>>>> 4. Contribute to documentation. >>> > >>>>> >>> > >>>>> Thanks, >>> > >>>>> Mohan >>> > >>>>> >>> > >>>>> On 3 November 2015 at 06:09, Martijn Verburg < >>> > martijnverburg at gmail.com >>> > >>>>> > >>> > >>>>> wrote: >>> > >>>>> >>> > >>>>> > Once you make the move it'll get more eyes and more PRs will >>> start >>> > to >>> > >>>>> > arrive (much like Jitwatch and jcountdown I suspect). >>> > >>>>> > >>> > >>>>> > Is there someone in this list who is fairly new and will go >>> through >>> > >>>>> Mani's >>> > >>>>> > doc? >>> > >>>>> > >>> > >>>>> > Cheers, >>> > >>>>> > Martijn >>> > >>>>> > >>> > >>>>> > On Monday, 2 November 2015, Mani Sarkar >>> > wrote: >>> > >>>>> > >>> > >>>>> > > Martijn, >>> > >>>>> > > >>> > >>>>> > > I'm in conversation with the guys about moving it, and after >>> > >>>>> Devoxx BE is >>> > >>>>> > > a better move I think although I would have liked it to be >>> > earlier. >>> > >>>>> > > >>> > >>>>> > > On a more important note, I was wondering if the contents of >>> the >>> > >>>>> pages I >>> > >>>>> > > shared were good, if not, happy to change them so that >>> adoptors >>> > >>>>> get the >>> > >>>>> > > right info. >>> > >>>>> > > >>> > >>>>> > > Cheers, >>> > >>>>> > > Mani >>> > >>>>> > > >>> > >>>>> > > On Mon, Nov 2, 2015 at 11:31 AM, Martijn Verburg < >>> > >>>>> > martijnverburg at gmail.com >>> > >>>>> > > > >>> > wrote: >>> > >>>>> > > >>> > >>>>> > >> Hey Mani, >>> > >>>>> > >> >>> > >>>>> > >> Ah, I wondered where that was being hosted. You're happy to >>> > move >>> > >>>>> that >>> > >>>>> > to >>> > >>>>> > >> the AdoptOpenJDK repo post Devoxx correct? I've added a >>> link to >>> > >>>>> this >>> > >>>>> > Kit >>> > >>>>> > >> in the wiki and have also added the OpenJDK IRC channel >>> link to >>> > >>>>> the >>> > >>>>> > wiki as >>> > >>>>> > >> well. >>> > >>>>> > >> >>> > >>>>> > >> Cheers, >>> > >>>>> > >> Martijn >>> > >>>>> > >> >>> > >>>>> > >> On 31 October 2015 at 09:34, Mani Sarkar < >>> sadhak001 at gmail.com >>> > >>>>> > >> > >>> wrote: >>> > >>>>> > >> >>> > >>>>> > >>> Hi all, >>> > >>>>> > >>> >>> > >>>>> > >>> I have put together this page on how to ... >>> > >>>>> > >>> >>> > >>>>> > >>> >>> > >>>>> > >>> >>> > >>>>> > >>> > >>>>> >>> > >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/how_to_contribute_to_adopt_openjdk_and_openjdk.html >>> > >>>>> > >>> >>> > >>>>> > >>> As a community we should feel free to amend the contents >>> as per >>> > >>>>> what >>> > >>>>> > >>> really is meant by contributions. >>> > >>>>> > >>> >>> > >>>>> > >>> Anything incorrect or missing - feel free to report here or >>> > >>>>> create a >>> > >>>>> > >>> pull request (see >>> > >>>>> > >>> >>> > >>>>> > >>> > >>>>> >>> > >>> https://neomatrix369.gitbooks.io/adoptopenjdk-getting-started-kit/content/en/how-to-navigate/contribute.html >>> > >>>>> > >>> ). >>> > >>>>> > >>> >>> > >>>>> > >>> Thanks for reading and contributing. >>> > >>>>> > >>> >>> > >>>>> > >>> Cheers, >>> > >>>>> > >>> Mani >>> > >>>>> > >>> >>> > >>>>> > >>> -- >>> > >>>>> > >>> @theNeomatrix369 * | >>> > >>>>> **Blog >>> > >>>>> > >>> ** | *LJC Associate >>> & LJC >>> > >>>>> > Advocate >>> > >>>>> > >>> (@adoptopenjdk & @adoptajsr programs) >>> > >>>>> > >>> *Meet-a-Project - *MutabilityDetector >>> > >>>>> > >>> * | **Bitbucket >>> > >>>>> > >>> * * | **Github >>> > >>>>> > >>> * * | **LinkedIn >>> > >>>>> > >>> * >>> > >>>>> > >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> > >>>>> > >>> >>> > >>>>> > >>> *Don't chase success, rather aim for "Excellence", and >>> success >>> > >>>>> will >>> > >>>>> > come >>> > >>>>> > >>> chasing after you!* >>> > >>>>> > >>> >>> > >>>>> > >> >>> > >>>>> > >> >>> > >>>>> > > >>> > >>>>> > > >>> > >>>>> > > -- >>> > >>>>> > > @theNeomatrix369 * | >>> > **Blog >>> > >>>>> > > ** | *LJC Associate & >>> LJC >>> > >>>>> Advocate >>> > >>>>> > > (@adoptopenjdk & @adoptajsr programs) >>> > >>>>> > > *Meet-a-Project - *MutabilityDetector >>> > >>>>> > > * | **Bitbucket >>> > >>>>> > > * * | **Github >>> > >>>>> > > * * | **LinkedIn >>> > >>>>> > > * >>> > >>>>> > > *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> > >>>>> > > >>> > >>>>> > > *Don't chase success, rather aim for "Excellence", and >>> success >>> > >>>>> will come >>> > >>>>> > > chasing after you!* >>> > >>>>> > > >>> > >>>>> > >>> > >>>>> > >>> > >>>>> > -- >>> > >>>>> > Cheers, Martijn (Sent from Gmail Mobile) >>> > >>>>> > >>> > >>>>> >>> > >>>> >>> > >>>> >>> > >>> >>> > >> >>> > > >>> > >>> >>> >>> >>> -- >>> @theNeomatrix369 * | **Blog >>> ** | *LJC Associate & LJC Advocate >>> (@adoptopenjdk & @adoptajsr programs) >>> *Meet-a-Project - *MutabilityDetector >>> * | **Bitbucket >>> * * | **Github >>> * * | **LinkedIn >>> * >>> *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ >>> >>> *Don't chase success, rather aim for "Excellence", and success will come >>> chasing after you!* >>> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Tue Nov 17 17:22:28 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Tue, 17 Nov 2015 17:22:28 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Hi Martijn, Try reloading the page again, it does not happen anymore, i just checked. It depends when you last checked it. Should have rebuild that page with the correct links now. Our older links will redirect to the new pages. Cheers, Mani -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Tue Nov 17 17:23:42 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Tue, 17 Nov 2015 17:23:42 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: S3 buckets maybe an option, if someone is happy to host our boxes ? Github can be slow. Cheers, Mani -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Wed Nov 18 12:43:53 2015 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Wed, 18 Nov 2015 04:43:53 -0800 (PST) Subject: JDK 9 b92 test results now available Message-ID: JDK 9 ea b92 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 6 differences from the b91 test results. No new testcase failures found. 0: /home/jtest/merge9/b91/jdk/JTwork pass: 5,257; fail: 23; error: 2; not run: 1,871 1: /home/jtest/merge9/b92/jdk/JTwork pass: 5,261; fail: 23; error: 1; not run: 1,878 0 1 Test pass --- java/lang/invoke/LFCaching/LFSingleThreadCachingTest.java error pass java/nio/Buffer/Basic.java --- pass java/util/Arrays/ArraysEqCmpTest.java --- pass javax/imageio/plugins/bmp/BMPPixelSpacingTest.java --- pass javax/management/Introspector/LegacyConstructorPropertiesTest.java --- pass jdk/internal/jimage/JImageReadTest.java 6 difference The hotspot test results contain 27 differences from the b91 test results. There are 4 testcase failures, these failures are under investigation. 0: /home/jtest/merge9/b91/hotspot/JTwork pass: 948; error: 3; not run: 44 1: /home/jtest/merge9/b92/hotspot/JTwork pass: 971; fail: 4; error: 3; not run: 46 0 1 Test --- pass compiler/compilercontrol/InlineMatcherTest.java --- pass compiler/compilercontrol/TestCompilerDirectivesCompatibilityBase.java --- fail compiler/compilercontrol/TestCompilerDirectivesCompatibilityCommandOff.java --- fail compiler/compilercontrol/TestCompilerDirectivesCompatibilityCommandOn.java --- fail compiler/compilercontrol/TestCompilerDirectivesCompatibilityFlag.java --- pass compiler/compilercontrol/commandfile/CompileOnlyTest.java --- pass compiler/compilercontrol/commandfile/ExcludeTest.java --- pass compiler/compilercontrol/commandfile/LogTest.java --- pass compiler/compilercontrol/commandfile/PrintTest.java --- pass compiler/compilercontrol/commands/CompileOnlyTest.java --- pass compiler/compilercontrol/commands/ExcludeTest.java --- pass compiler/compilercontrol/commands/LogTest.java --- pass compiler/compilercontrol/commands/PrintTest.java --- pass compiler/compilercontrol/directives/CompileOnlyTest.java --- pass compiler/compilercontrol/directives/ExcludeTest.java --- pass compiler/compilercontrol/directives/LogTest.java --- pass compiler/compilercontrol/directives/PrintTest.java --- pass compiler/compilercontrol/jcmd/AddAndRemoveTest.java --- pass compiler/compilercontrol/jcmd/AddCompileOnlyTest.java --- pass compiler/compilercontrol/jcmd/AddExcludeTest.java --- pass compiler/compilercontrol/jcmd/AddLogTest.java --- pass compiler/compilercontrol/jcmd/AddPrintAssemblyTest.java --- pass compiler/compilercontrol/jcmd/ClearDirectivesStackTest.java --- pass compiler/compilercontrol/mixed/RandomCommandsTest.java --- pass compiler/compilercontrol/parser/DirectiveParser.java --- pass compiler/intrinsics/IntrinsicDisabledTest.java --- fail serviceability/dcmd/compiler/CompilerDirectivesDCMDTest.java 27 differences The langtools test results contain 1 difference from the b91 test results. No new testcase failures found. 0: /home/jtest/merge9/b91/langtools/JTwork pass: 3,296; not run: 50 1: /home/jtest/merge9/b92/langtools/JTwork pass: 3,297; not run: 50 0 1 Test --- pass tools/javac/cast/8141343/T8141343.java 1 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/b92/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From sadhak001 at gmail.com Wed Nov 18 21:25:36 2015 From: sadhak001 at gmail.com (Mani Sarkar) Date: Wed, 18 Nov 2015 21:25:36 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: I have reported this issue (404 errors) to the dev at GitBook.IO, and its been addressed as we speak. Cheers, Mani On Tue, Nov 17, 2015 at 5:22 PM, Mani Sarkar wrote: > Hi Martijn, > > Try reloading the page again, it does not happen anymore, i just checked. > It depends when you last checked it. Should have rebuild that page with the > correct links now. Our older links will redirect to the new pages. > > Cheers, > Mani > -- @theNeomatrix369 * | **Blog ** | *LJC Associate & LJC Advocate (@adoptopenjdk & @adoptajsr programs) *Meet-a-Project - *MutabilityDetector * | **Bitbucket * * | **Github * * | **LinkedIn * *Come to Devoxx UK 2016:* http://www.devoxx.co.uk/ *Don't chase success, rather aim for "Excellence", and success will come chasing after you!* -------------- next part -------------- An HTML attachment was scrubbed... URL: From martijnverburg at gmail.com Thu Nov 19 08:38:00 2015 From: martijnverburg at gmail.com (Martijn Verburg) Date: Thu, 19 Nov 2015 08:38:00 +0000 Subject: How to contribute to the Adopt OpenJDK and OpenJDK ? In-Reply-To: References: Message-ID: Hi John, I believe that some of the sub trees/forests have Netbeans configurations it would be nice to have that supported as well. Cheers, Martijn On 17 November 2015 at 17:38, John Patrick wrote: > I'm hoping I can iron out the kinks with the vagrant setup as that is a > sub 400MB download and means it can be easily deleted and recreated if > something goes wrong. So hopefully new users won't need to download large > VMs. > > Also as it more closely mimics the manual setup steps, future build > changes can be more easily incorporated, i.e. less smoke and mirrors than > using chef or puppet. > > I'm looking at getting a Eclipse and IntelliJ projects working. Does > anyone else thing any other IDE should be supported? > > John > > > On 17 November 2015 at 17:23, Mani Sarkar wrote: > >> S3 buckets maybe an option, if someone is happy to host our boxes ? >> Github can be slow. >> >> Cheers, >> Mani >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From abdul.kolarkunnu at oracle.com Fri Nov 27 04:12:34 2015 From: abdul.kolarkunnu at oracle.com (Muneer Kolarkunnu) Date: Thu, 26 Nov 2015 20:12:34 -0800 (PST) Subject: JDK 9 b93 test results now available Message-ID: <1e0e4bc6-cade-42ea-838e-c462f301a2ac@default> JDK 9 ea b93 test results are now available at http://www.java.net/download/openjdk/testresults/9/testresults.html The jdk test results contain 40 differences from the b92 test results. No new testcase failures found. 0: /home/jtest/merge9/b92/jdk/JTwork pass: 5,261; fail: 23; error: 1; not run: 1,878 1: /home/jtest/merge9/b93/jdk/JTwork pass: 5,293; fail: 23; error: 1; not run: 1,884 0 1 Test --- pass java/lang/String/Chars.java --- pass java/lang/String/CompactString/CharAt.java --- pass java/lang/String/CompactString/CodePointAt.java --- pass java/lang/String/CompactString/CodePointBefore.java --- pass java/lang/String/CompactString/CodePointCount.java --- pass java/lang/String/CompactString/CompareTo.java --- pass java/lang/String/CompactString/CompareToIgnoreCase.java --- pass java/lang/String/CompactString/Concat.java --- pass java/lang/String/CompactString/Contains.java --- pass java/lang/String/CompactString/EndsWith.java --- pass java/lang/String/CompactString/Equals.java --- pass java/lang/String/CompactString/EqualsIgnoreCase.java --- pass java/lang/String/CompactString/GetChars.java --- pass java/lang/String/CompactString/IndexOf.java --- pass java/lang/String/CompactString/Intern.java --- pass java/lang/String/CompactString/LastIndexOf.java --- pass java/lang/String/CompactString/Length.java --- pass java/lang/String/CompactString/Numbers.java --- pass java/lang/String/CompactString/OffsetByCodePoints.java --- pass java/lang/String/CompactString/RegionMatches.java --- pass java/lang/String/CompactString/Replace.java --- pass java/lang/String/CompactString/SerializationTest.java --- pass java/lang/String/CompactString/Split.java --- pass java/lang/String/CompactString/StartsWith.java --- pass java/lang/String/CompactString/SubString.java --- pass java/lang/String/CompactString/ToCharArray.java --- pass java/lang/String/CompactString/ToLowerCase.java --- pass java/lang/String/CompactString/ToUpperCase.java --- pass java/lang/String/CompactString/Trim.java --- pass java/lang/String/CompactString/VMOptionsTest.java --- pass java/lang/String/CompactString/ValueOf.java --- pass java/lang/StringBuffer/CompactStringBuffer.java --- pass java/lang/StringBuffer/CompactStringBufferSerialization.java --- pass java/lang/StringBuilder/CompactStringBuilder.java --- pass java/lang/StringBuilder/CompactStringBuilderSerialization.java --- pass java/security/SecureRandom/DefaultProvider.java pass --- java/util/Arrays/ParallelPrefix.java pass --- java/util/BitSet/BitSetStreamTest.java pass --- java/util/stream/test/org/openjdk/tests/java/util/stream/FlatMapOpTest.java pass --- java/util/stream/test/org/openjdk/tests/java/util/stream/IntPrimitiveOpsTests.java 40 differences The hotspot test results contain 14 differences from the b92 test results. There are 6 testcase failures, these failures are under investigation. 0: /home/jtest/merge9/b92/hotspot/JTwork pass: 971; fail: 4; error: 3; not run: 46 1: /home/jtest/merge9/b93/hotspot/JTwork pass: 971; fail: 7; error: 3; not run: 46 0 1 Test pass fail compiler/c2/8004741/Test8004741.java fail pass compiler/compilercontrol/TestCompilerDirectivesCompatibilityCommandOff.java fail pass compiler/compilercontrol/TestCompilerDirectivesCompatibilityCommandOn.java fail pass compiler/compilercontrol/TestCompilerDirectivesCompatibilityFlag.java --- pass compiler/intrinsics/string/TestStringIntrinsics.java pass --- compiler/jvmci/events/JvmciCompleteInitializationTest.java pass fail compiler/loopopts/TestCastIINoLoopLimitCheck.java pass fail compiler/runtime/7196199/Test7196199.java pass fail gc/TestNUMAPageSize.java pass fail gc/g1/TestEagerReclaimHumongousRegionsClearMarkBits.java pass fail gc/g1/TestLargePageUseForAuxMemory.java --- pass runtime/Annotations/TestAnnotatedStringEncoding.java --- pass runtime/CommandLine/IgnoreUnrecognizedVMOptions.java --- pass runtime/SharedArchiveFile/CdsDifferentCompactStrings.java 14 differences The langtools test results contain 12 differences from the b92 test results. No new testcase failures found. 0: /home/jtest/merge9/b92/langtools/JTwork pass: 3,297; not run: 50 1: /home/jtest/merge9/b93/langtools/JTwork pass: 3,309; not run: 49 0 1 Test --- pass tools/javac/OverrideChecks/T8139255.java --- pass tools/javac/annotations/typeAnnotations/classfile/InstanceInitializer.java --- pass tools/javac/annotations/typeAnnotations/classfile/StaticInitializer.java --- pass tools/javac/classfiles/attributes/annotations/RuntimeParameterAnnotationsForLambdaTest.java --- pass tools/javac/generics/inference/8141613/T8141613.java --- pass tools/javac/lambda/SE5AnnotationsOnLambdaParameters.java --- pass tools/javac/lambda/T8129740/AllowEnclosingVarCaptureTest.java --- pass tools/javac/lambda/T8129740/CaptureInCtorChainingTest.java --- pass tools/javac/lambda/T8129740/QualifiedThisAccessTest.java --- pass tools/javac/lambda/T8129740/SourceToSourceTranslationTest.java --- pass tools/javac/lambda/methodReference/IntersectionTypeReceiverTest.java --- pass tools/javac/lambda/methodReference/IntersectionTypeReceiverTest2.java 12 differences The nashorn test result is available at http://download.java.net/openjdk/testresults/9/archives/b93/emailable-report.html -- Regards, Abdul Muneer Quality Engineer Oracle, Bangalore, India -------------- next part -------------- An HTML attachment was scrubbed... URL: From rory.odonnell at oracle.com Fri Nov 27 12:24:14 2015 From: rory.odonnell at oracle.com (Rory O'Donnell) Date: Fri, 27 Nov 2015 12:24:14 +0000 Subject: Early Access b93 is available for JDK 9 on java.net Message-ID: <56584B6E.7090304@oracle.com> Hi All, Since my last message about JDK 9 build b88, a number of new JEPs have been integrated into JDK 9 b93 available here . I'd like to point you to a few that are now available for testing in this JDK 9 Early Access build: JEP 254: Compact Strings (http://openjdk.java.net/jeps/254) This JEP adopts a more space-efficient internal representation for strings. We propose to change the internal representation of the String class from a UTF-16 char array to a byte array plus an encoding-flag field. The new String class will store characters encoded either as ISO-8859-1/Latin-1 (one byte per character), or as UTF-16 (two bytes per character), based upon the contents of the string. The encoding flag will indicate which encoding is used. JEP 165: Compiler Control (http://openjdk.java.net/jeps/165) This JEP proposes an improved way to control the JVM compilers. It enables runtime manageable, method dependent compiler flags. (Immutable for the duration of a compilation.) Method-context dependent control of the compilation process is a powerful tool for writing small contained JVM compiler tests that can be run without restarting the entire JVM. It is also very useful for creating workarounds for bugs in the JVM compilers. JEP 243: Java-Level JVM Compiler Interface (http://openjdk.java.net/jeps/243) This JEP instruments the data flows within the JVM which are used by the JIT compiler to allow Java code to observe, query, and affect the JVM's compilation process and its associated metadata. JEP 268: XML Catalog API (http://openjdk.java.net/jeps/268) This JEP develops a standard XML Catalog API that supports the OASIS XML Catalogs standard, v1.1. The API will define catalog and catalog-resolver abstractions which can be used with the JAXP processors that accept resolvers. Existing libraries or applications that use the internal API will need to migrate to the new API in order to take advantage of the new features. Rgds, Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -------------- next part -------------- An HTML attachment was scrubbed... URL: