Merging jdk7-b75 into Jigsaw
Kelly O'Hair
Kelly.Ohair at Sun.COM
Tue Nov 10 14:05:48 PST 2009
Mark Reinhold wrote:
>> From: Mark Reinhold <mr at sun.com>
>> Date: Fri, 06 Nov 2009 11:32:37 -0800
>
>>> From: Mark Reinhold <mr at sun.com>
>>> Date: Fri, 06 Nov 2009 10:22:17 -0800
>>> ...
>>>
>>> I'm starting to suspect something in my build environment. I'll try a
>>> pure M5 build, without any Jigsaw changes, and see what happens.
>> Yep, same problem, but then I recalled the recent ALT_JDK_IMPORT_PATH
>> issue and noticed that my build script was still setting it. Removing
>> that setting fixed the problem, though I'm not completely sure why.
>
> When something starts working for a reason unknown, beware ...
>
> That wasn't the problem after all. I'm seeing this again in a merged
> Jigsaw+M5 forest.
>
> After enabling some ant verbosity I found that, when building jaxws,
> ant defines the javac -classpath argument as
>
> $BUILD/jaxws/build/classes:${RANDOM_ANT_JARS}:$BUILD/bootjdk/j2sdk-image/lib/tools.jar
>
> in a plain M5 build. In a Jigsaw+M5 build, however, the tools.jar
> element is omitted, which certainly explains the failure I'm seeing.
>
> Can someone with more ant expertise than I suggest how to proceed?
Could be painful ant bite #3 in my list:
http://blogs.sun.com/kto/entry/painful_ant_bite_a_generous
We need to explicitly exclude the Ant runtime classpath entries
and be explicit about everything on the classpath:
<javac> uses to <javac includeAntRuntime="false">
I will look at the jaxws and jaxp ant scripts and see if the fix is
simple.
-kto
>
> Full logs available on request.
>
> - Mark
More information about the jigsaw-dev
mailing list