ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby" <ru...@us.ibm.com>
Subject Re: [BUG?] Java Task adds Ant Classpath when forking
Date Mon, 15 Jan 2001 16:00:49 GMT
> We are caught between a rock and a hard place then,
> because even "last" gives me a problem when running
> weblogic.

Then don't run weblogic.  There probably are better alternatives out there,
anyway.

...Just kidding.  ;-)

> server:
>     [wlrun]
>
***************************************************************************
>     [wlrun] The WebLogic Server did not start up properly.
>     [wlrun] Reason: Trying to start the server dynamically, specifying
> weblogic.class.path, but regular (non-boot) server classes found in
> Java -classpath.
>    [wlrun]
>
***************************************************************************
>
> BUILD FAILED
>
> Quite why weblogic has this behaviour, I'm not sure.

Probably to protect their support team from dumb users.

> It works, if I run ant with build.sysclasspath=ignore,
> but we do have an issue. I can change the wlrun task
> but I now need to control a java task on an individual
> basis rather than by the global property, whose
> interaction is buried in the Path object.
>
> Let me know what you think. I'll work something up if
> you are busy.

For now, perhaps the default for the "java" task should be changed to
ignore?

Not a complete solution, but it restores another aspect of backwards
compatibility.  It would mean that you would not have to worry about
build.sysclasspath, and I won't be able to run tinderbox builds which
execute weblogic...

- Sam Ruby


Mime
View raw message