Jeff Turner wrote: > > On Mon, Dec 17, 2001 at 11:28:43AM -0000, Morrison, John wrote: > > > -----Original Message----- > > > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > > Sent: Monday, 17 December 2001 11:26 am > > > To: [EMAIL PROTECTED] > > > Subject: RE: Building and Classpath > > > > > > > > > John Morrison wrote > > > > > > > > Solution D: fix the ant Available task (which has been > > > rejected(?) by the > > > > ant team... > > > > > > > Hmm, yes that would be great! But, the question is, is it a bug? > > > AFAIK, the Ant Available task is able to search only in a > > > given classpath > > > or to search in a given classpath and respect the user classpath. > > > The bad thing for us (and this can be seen as a bug) is that > > > the Available task *always* searches the standard java classes. > > > > > > Carsten > > > > > > > Maybe adding a "do-not-search-classpath" option would be something to > > consider? > > If your build.xml contains: > > <property name="build.sysclasspath" value="ignore"/> > > Would that help? > No, unfortunately not. When "build.sysclasspath" is set to ignore, the user classpath is ignored, but not the standard JDK classes. What I want to have is a possibility to say: <available property="working" classname="java.net.URL"> <classpath refid="classpath"/> </available> which gives me - depending on a property a true or false. But regardless of the "build.sysclasspath" property, the above always returns true.
Carsten > > (IMHO the whole thing should be done with properties. Relying on > classpaths is inherently error-prone:) > > --Jeff > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
