Merging jdk7-b75 into Jigsaw
Jonathan Gibbons
Jonathan.Gibbons at Sun.COM
Tue Nov 10 13:26:12 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?
>
> Full logs available on request.
>
> - Mark
>
Mark,
The jaxws build.xml file does not set classpath for javac, so you are
getting the default classpath set by Ant. Since jaxws does not set the
classpath, I would presume that jaxws does not depend on anything in
tools.jar. Do you know if that is the case or not? If it does depend on
stuff in tools.jar, it ought to consider setting the classpath
explicitly to include any necessary classes coming from langtools.
What is the failure you are seeing?
-- Jon
More information about the jigsaw-dev
mailing list