Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Well, looking at https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/34/consoleText I see os.arch=arm sun.arch.abi=gnueabihf While https://builds.apache.org/computer/ubuntu1/systemInfo is an amd64 system. ;) cheers, dalibor topic On 17.01.2014 18:56, Robert Scholte wrote: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/34/ this seems to be the latest valid run. A few plugins fail due the JDK8 related (hence, that's why this job was created). It took 6 hr 23 min. to finish this job. Stephen Connolly also mentions the following: isn't ubuntu_ARM_12 an ARM machine and not amd64 ubuntu1-6 are all amd64 AFAIR Maybe these systems are too different to make a comparison, would be nice if we could benchmark it somehow on equivalent environments. Robert Op Fri, 17 Jan 2014 18:35:31 +0100 schreef dalibor topic dalibor.to...@oracle.com: On 17.01.2014 18:17, Robert Scholte wrote: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/ #423 hr 50 minubuntu_ARM_12 Looking at https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/42/console is seems like there are some network connection issues: [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [INFO] snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT: checking for updates from central [WARNING] repository metadata for: 'snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT' could not be retrieved from repository: central due to an error: Error transferring file: repo.maven.apache.org etc. If something's timing out, that might explain the difference. cheers, dalibor topic -- http://www.oracle.com Dalibor Topic | Principal Product Manager Phone: +494089091214 tel:+494089091214 | Mobile: +491737185961 tel:+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 Geschäftsführer: Jürgen Kunz 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 http://www.oracle.com/commitment Oracle is committed to developing practices and products that help protect the environment - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
On 17.01.2014 18:17, Robert Scholte wrote: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/ #423 hr 50 minubuntu_ARM_12 Looking at https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/42/console is seems like there are some network connection issues: [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [INFO] snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT: checking for updates from central [WARNING] repository metadata for: 'snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT' could not be retrieved from repository: central due to an error: Error transferring file: repo.maven.apache.org etc. If something's timing out, that might explain the difference. cheers, dalibor topic -- http://www.oracle.com Dalibor Topic | Principal Product Manager Phone: +494089091214 tel:+494089091214 | Mobile: +491737185961 tel:+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 Geschäftsführer: Jürgen Kunz 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 http://www.oracle.com/commitment Oracle is committed to developing practices and products that help protect the environment - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Rory, I've just submitted the javadoc issue, Bug ID: 9009740 Regarding the performance, here are some stats: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.7/ https://builds.apache.org/computer/ubuntu1/systemInfo #146 Jan 12, 2014 9:58:11 PM 4 MB 1 hr 5 min ubuntu1 #142 Jan 10, 2014 9:44:34 PM 4 MB 1 hr 2 min ubuntu3 #138 Jan 3, 2014 7:46:49 AM 4 MB 1 hr 4 min ubuntu3 #135 Jan 2, 2014 12:26:26 PM 4 MB 1 hr 1 min ubuntu3 #134 Jan 2, 2014 6:46:34 AM 4 MB 1 hr 24 min ubuntu3 https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/ #42 3 hr 50 min ubuntu_ARM_12 #41 4 min 21 secubuntu_ARM_12 #40 3 hr 54 min ubuntu_ARM_12 #39 4 min 44 secubuntu_ARM_12 #38 4 min 23 secubuntu_ARM_12 #37 3 hr 16 min ubuntu_ARM_12 #36 3 hr 11 min ubuntu_ARM_12 #35 3 hr 17 min ubuntu_ARM_12 #34 6 hr 23 min ubuntu_ARM_12 #33 3 hr 4 min ubuntu_ARM_12 #32 3 hr 10 min ubuntu_ARM_12 #31 5 hr 59 min ubuntu_ARM_12 Some additional info: The only difference should be the JDK. Right now the ubuntu_ARM_12 is down, so I can't give any details about that system. I've only listed the completed and successful jdk-1.7 runs, jdk-1.8 still has failures. The difference is huge, even though these are different machines. It would be better if both were executed on the same environment, but that's probably not possible right now. thanks, Robert Op Thu, 16 Jan 2014 12:13:31 +0100 schreef Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com: Hi Robert, Any update on details on the performance issue ? Secondly , did you log a bug for the javadoc issues ? Rgds, Rory On 14/01/2014 13:21, Rory O'Donnell Oracle, Dublin Ireland wrote: Hi Robert, Comments below. On 13/01/2014 19:36, Robert Scholte wrote: Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. Can you log a web bug for this please. let me know the Incident number and I can monitor it's progress. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. I noticed https://bugs.openjdk.java.net/browse/JDK-8031572 is logged via a web bug from tche...@apache.org , thank you for that. Dalibor has written in his blog how to monitor your issues in the JDK Bug System - http://robilad.livejournal.com/139637.html. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. Can you provide more details, log a bug ? Rgds, Rory We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/34/ this seems to be the latest valid run. A few plugins fail due the JDK8 related (hence, that's why this job was created). It took 6 hr 23 min. to finish this job. Stephen Connolly also mentions the following: isn't ubuntu_ARM_12 an ARM machine and not amd64 ubuntu1-6 are all amd64 AFAIR Maybe these systems are too different to make a comparison, would be nice if we could benchmark it somehow on equivalent environments. Robert Op Fri, 17 Jan 2014 18:35:31 +0100 schreef dalibor topic dalibor.to...@oracle.com: On 17.01.2014 18:17, Robert Scholte wrote: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/ #423 hr 50 minubuntu_ARM_12 Looking at https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/42/console is seems like there are some network connection issues: [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [WARNING] Unable to get resource 'org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:pom:2.4.2' from repository central (http://repo.maven.apache.org/maven2): Error transferring file: repo.maven.apache.org [INFO] snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT: checking for updates from central [WARNING] repository metadata for: 'snapshot org.apache.maven.plugins.maven-javadoc-plugin.unit:stylesheetfile-test:1.0-SNAPSHOT' could not be retrieved from repository: central due to an error: Error transferring file: repo.maven.apache.org etc. If something's timing out, that might explain the difference. cheers, dalibor topic - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
On 17/01/2014 17:17, Robert Scholte wrote: Hi Rory, I've just submitted the javadoc issue, Bug ID: 9009740 Hi Robert above can be tracked at : https://bugs.openjdk.java.net/browse/JDK-8032205 As for the performance issue , we need to compare apples with apples first, do let us know if there is still an issue once you have a suitable setup. Rgds,Rory Regarding the performance, here are some stats: https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.7/ https://builds.apache.org/computer/ubuntu1/systemInfo #146 Jan 12, 2014 9:58:11 PM 4 MB 1 hr 5 minubuntu1 #142 Jan 10, 2014 9:44:34 PM 4 MB 1 hr 2 minubuntu3 #138 Jan 3, 2014 7:46:49 AM 4 MB 1 hr 4 minubuntu3 #135 Jan 2, 2014 12:26:26 PM 4 MB 1 hr 1 minubuntu3 #134 Jan 2, 2014 6:46:34 AM 4 MB 1 hr 24 minubuntu3 https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/ #423 hr 50 minubuntu_ARM_12 #414 min 21 secubuntu_ARM_12 #403 hr 54 minubuntu_ARM_12 #394 min 44 secubuntu_ARM_12 #384 min 23 secubuntu_ARM_12 #373 hr 16 minubuntu_ARM_12 #363 hr 11 minubuntu_ARM_12 #353 hr 17 minubuntu_ARM_12 #346 hr 23 minubuntu_ARM_12 #333 hr 4 minubuntu_ARM_12 #323 hr 10 minubuntu_ARM_12 #315 hr 59 minubuntu_ARM_12 Some additional info: The only difference should be the JDK. Right now the ubuntu_ARM_12 is down, so I can't give any details about that system. I've only listed the completed and successful jdk-1.7 runs, jdk-1.8 still has failures. The difference is huge, even though these are different machines. It would be better if both were executed on the same environment, but that's probably not possible right now. thanks, Robert Op Thu, 16 Jan 2014 12:13:31 +0100 schreef Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com: Hi Robert, Any update on details on the performance issue ? Secondly , did you log a bug for the javadoc issues ? Rgds, Rory On 14/01/2014 13:21, Rory O'Donnell Oracle, Dublin Ireland wrote: Hi Robert, Comments below. On 13/01/2014 19:36, Robert Scholte wrote: Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. Can you log a web bug for this please. let me know the Incident number and I can monitor it's progress. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. I noticed https://bugs.openjdk.java.net/browse/JDK-8031572 is logged via a web bug from tche...@apache.org , thank you for that. Dalibor has written in his blog how to monitor your issues in the JDK Bug System - http://robilad.livejournal.com/139637.html. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. Can you provide more details, log a bug ? Rgds, Rory We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Robert, Any update on details on the performance issue ? Secondly , did you log a bug for the javadoc issues ? Rgds, Rory On 14/01/2014 13:21, Rory O'Donnell Oracle, Dublin Ireland wrote: Hi Robert, Comments below. On 13/01/2014 19:36, Robert Scholte wrote: Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. Can you log a web bug for this please. let me know the Incident number and I can monitor it's progress. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. I noticed https://bugs.openjdk.java.net/browse/JDK-8031572 is logged via a web bug from tche...@apache.org , thank you for that. Dalibor has written in his blog how to monitor your issues in the JDK Bug System - http://robilad.livejournal.com/139637.html. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. Can you provide more details, log a bug ? Rgds, Rory We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see:
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Robert/Tony, Can you gives us an understanding of the impact to Maven of bug https://bugs.openjdk.java.net/browse/JDK-8031572 Rgds,Rory On 16/01/2014 11:13, Rory O'Donnell Oracle, Dublin Ireland wrote: Hi Robert, Any update on details on the performance issue ? Secondly , did you log a bug for the javadoc issues ? Rgds, Rory On 14/01/2014 13:21, Rory O'Donnell Oracle, Dublin Ireland wrote: Hi Robert, Comments below. On 13/01/2014 19:36, Robert Scholte wrote: Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. Can you log a web bug for this please. let me know the Incident number and I can monitor it's progress. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. I noticed https://bugs.openjdk.java.net/browse/JDK-8031572 is logged via a web bug from tche...@apache.org , thank you for that. Dalibor has written in his blog how to monitor your issues in the JDK Bug System - http://robilad.livejournal.com/139637.html. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. Can you provide more details, log a bug ? Rgds, Rory We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
On Thu, 16 Jan 2014 14:04:58 + Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com wrote: Hi Robert/Tony, Can you gives us an understanding of the impact to Maven of bug https://bugs.openjdk.java.net/browse/JDK-8031572 Hi Rory, Maybe just reordering jar entries will fix this if I cleary understand Weijun comment on the issue. The bug was detected on a tampered jar so on a integration test so the impact should be low if people use *normal* jar. I will try to reorder the jar entries of the tampered jar and come back to you just after. Best regards, tony. -- Tony Chemit tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: che...@codelutin.com twitter: https://twitter.com/tchemit - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Thanks Tony, I will update the bug when you send feedback. Rgds,Rory On 16/01/2014 14:27, Tony Chemit wrote: On Thu, 16 Jan 2014 14:04:58 + Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com wrote: Hi Robert/Tony, Can you gives us an understanding of the impact to Maven of bug https://bugs.openjdk.java.net/browse/JDK-8031572 Hi Rory, Maybe just reordering jar entries will fix this if I cleary understand Weijun comment on the issue. The bug was detected on a tampered jar so on a integration test so the impact should be low if people use *normal* jar. I will try to reorder the jar entries of the tampered jar and come back to you just after. Best regards, tony. -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Robert, Comments below. On 13/01/2014 19:36, Robert Scholte wrote: Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. Can you log a web bug for this please. let me know the Incident number and I can monitor it's progress. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. I noticed https://bugs.openjdk.java.net/browse/JDK-8031572 is logged via a web bug from tche...@apache.org , thank you for that. Dalibor has written in his blog how to monitor your issues in the JDK Bug System - http://robilad.livejournal.com/139637.html. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. Can you provide more details, log a bug ? Rgds, Rory We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Rory, The Apache Maven team has introduced a wiki page[1] to keep track of JDK8 specific issues. These are results when we started to build+test all our plugins with JDK8. We see that the javadoc executable has become stricter. Especially the reference not found is tricky, since there's a good chance the sources are from a dependency, something we cannot change. The only workaround I could find was adding a excludePackageNames for the specific class, but this will exclude all classes of that package Another issue with the javadoc executable is that the excludedocfilessubdir argument is ignored (on Win7). This seems to be regression. There is probably also regression in the jarsigner executable when verifying fails, see MJARSIGNER-30. We don't have serious benchmarks, but until now JDK8 has always been slower compared to JDK7. We've only started with testing the Maven plugins together with JDK8, we could add some other projects as well. thanks, Robert [1] https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade [2] https://jira.codehaus.org/browse/MJARSIGNER-30 Op Mon, 06 Jan 2014 12:16:33 +0100 schreef Rory O'Donnell Oracle, Dublin ireland rory.odonn...@oracle.com: Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test.
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Kristian, Thank you for your comments. On 01/ 3/14 02:12 PM, Kristian Rosenvold wrote: We found the issue already, thanks for the bump in priority ! no problem. The jdk issue tracker does not allow us much in the way of features (like issue watching !) Yes, there is room for improvement there. In the mean time Dalibor wrote in his blog about tracking your issues In The JDK Bug System: http://robilad.livejournal.com/139637.html There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. I think Alan's comment was more wishful thinking, finding bugs early is in everyone's interest. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) I would love to discuss your testing with you in detail? We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. Delighted to hear that! Obviously, the later bugs are found the more likely they will get fixed in an update release. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Thanks, Rory Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds, Rory O'Donnell Senior Quality Engineering Manager Java Platform Group Oracle EMEA , Block P5, East Point Business Park, Dublin 3 Phone: +353 (0)1 8033887
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com mailto:rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
We found the issue already, thanks for the bump in priority ! The jdk issue tracker does not allow us much in the way of features (like issue watching !) There is a comment I'd like to make about the issue comment of us reporting this issue 6 months ago. 6 months ago was M7, labeled as feature complete according to the JDK8 plan. Our code base is *huge* and there's a fair amount of weird stuff going on, and I think most of us on the maven team are reluctant to start testing with something that is just feature complete. Finding and reporting this *one* issue took quite some effort, since we're usually talking about tests written for *other* purposes that break; and they break in weird places highly unexpected manners. So realistically we're testing at the earliest level we're comfortable with (which I find is M8-ish). Less complex projects are probably a bit more risk-willing than us :) We have quite some momentum in our jdk8 testing now, and there's quite a few of us who seem intent on verifying *everything* in good time before GA. I know I'll be picking up the verification once JDK-8030781 https://bugs.openjdk.java.net/browse/JDK-8030781 gets released into a nightly. Kristian 2014/1/3 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com Hi Kristian, I am following sun bug 9009028, https://bugs.openjdk.java.net/browse/JDK-8030781 Rgds,Rory On 31/12/2013 20:38, Kristian Rosenvold wrote: Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi Bernd, On 30/12/2013 17:57, Bernd Eckenfels wrote: Hello Rory, after having repeatingly problems in our WebStart Application (die to changed behaviour in Updates) I have tested with U60 and I havent seen any new problems compared to U45. I did not do server side (performance) tests yet. Are the issues you found on u45 already logged with us ? With JDK8 I did only a few smaller (default maven JAR phase based) compile tests (for example adding OracleJDK8 to the build environemnt matrix on Travis-CI.org - but without using -target 1.8). I havent seen problems in this area. I think it is a but confusing that the manage site list dialog contains a textfield (which allows edit) when the list is empty but I guess thats not a critical problem. I'm not sure I understand the above can you elaborate for me ? Thanks for your help. Rgds,Rory Greetings Bernd Am 30.12.2013, 13:19 Uhr, schrieb Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com: Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Been meaning to answer this mail for a few days, but I've been far too busy skiing in the norwegian mountains :) We have some fairly extensive tests and integration tests that would, to a large extent, also function as a verification of jdk8 compatibility. Unfortunately most of them get stuck at sun bug 9009028, which I filed about a week ago. So while this bug is open, it may hide other problems. So with my tester hat on; we have one known bug that potentially hides interesting stuff. Kristian 2013/12/30 Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/ pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- Rgds,Rory O'Donnell Quality Engineering Manager Oracle EMEA , Dublin, Ireland
Re: JDK 8 Build 121 JDK 7 Update 60 build 02 are available on java.net
Hello Rory, after having repeatingly problems in our WebStart Application (die to changed behaviour in Updates) I have tested with U60 and I havent seen any new problems compared to U45. I did not do server side (performance) tests yet. With JDK8 I did only a few smaller (default maven JAR phase based) compile tests (for example adding OracleJDK8 to the build environemnt matrix on Travis-CI.org - but without using -target 1.8). I havent seen problems in this area. I think it is a but confusing that the manage site list dialog contains a textfield (which allows edit) when the list is empty but I guess thats not a critical problem. Greetings Bernd Am 30.12.2013, 13:19 Uhr, schrieb Rory O'Donnell Oracle, Dublin Ireland rory.odonn...@oracle.com: Hi, I am from the OpenJDK QA group at Oracle, and I'm trying to get an idea about how much community testing is happening on JDK 8 EA builds (either those published by Oracle, or your own) and to encourage more of it to happen see: http://mail.openjdk.java.net/pipermail/quality-discuss/2013-November/000152.html I'm curious if you have begun testing against JDK 8 or JDK 7u60 EA builds, if you've run into showstopper issues, and if you'd like to continue to discuss the subject on the quality-discuss mailing list in OpenJDK, of course. I am aware of https://bugs.openjdk.java.net/browse/JDK-8030781 , if there are any other issues please let me know. JDK 8 Build b121 Early Access Build is now available for download http://jdk8.java.net/download.html test. JDK 7u60 b02 Early Access Build is also available for download https://jdk7.java.net/download.html test. Rgds,Rory -- http://www.zusammenkunft.net - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
