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
