JDK 8 Build 121 & JDK 7 Update 60 build 02 are available on java.net

Tue Jan 14 06:38:09 PST 2014

Hi Robert,

With regard to your javadoc issues, I am cc'ing the javadocs mailing list.

Rgds, Rory

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.
>
snip
>
> 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.odonnell at 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.odonnell at oracle.com <mailto:rory.odonnell at 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.odonnell at oracle.com <mailto:rory.odonnell at 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
>>>
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe at maven.apache.org
> For additional commands, e-mail: dev-help at maven.apache.org
>

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland