You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Matt Coarr <mc...@mitre.org> on 2002/04/05 17:39:49 UTC

classpath elements, properties, and interoperability

Hello,

I had been using a property to reference my classpath as a string value. 
 So this was being used with the javac task and with the exec and execon 
tasks (to call the ejbc command under the iplanet app server).

Then I tried to switch over to using the classpath element -- it's more 
flexible, more readable, and just a better way to do it.  However I ran 
into a problem.  How do I pass a value from a classpath element to an 
external command or a task that isn't aware of classpath elements.  The 
javac task includes the classpathref that makes this easy, but using 
this value seems difficult/impossible with exec/execon.  Any 
suggestions?  Perhaps there is a function that can be used to convert a 
classpath element to a string value?? :-)

Matt



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: classpath elements, properties, and interoperability

Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
uh, that should be:

    <property name="path.string" refid="some.path"/>

sorry 'bout that.

----- Original Message -----
From: "Erik Hatcher" <ja...@ehatchersolutions.com>
To: "Ant Users List" <an...@jakarta.apache.org>
Sent: Friday, April 05, 2002 11:05 AM
Subject: Re: classpath elements, properties, and interoperability


> <path id="some.path">
>   .
>   .
>   .
> </path>
>
> <property "path.string" refid="some.path"/>
>
> voila!  :)
>
>
>
> ----- Original Message -----
> From: "Matt Coarr" <mc...@mitre.org>
> To: <an...@jakarta.apache.org>
> Sent: Friday, April 05, 2002 10:39 AM
> Subject: classpath elements, properties, and interoperability
>
>
> > Hello,
> >
> > I had been using a property to reference my classpath as a string value.
> >  So this was being used with the javac task and with the exec and execon
> > tasks (to call the ejbc command under the iplanet app server).
> >
> > Then I tried to switch over to using the classpath element -- it's more
> > flexible, more readable, and just a better way to do it.  However I ran
> > into a problem.  How do I pass a value from a classpath element to an
> > external command or a task that isn't aware of classpath elements.  The
> > javac task includes the classpathref that makes this easy, but using
> > this value seems difficult/impossible with exec/execon.  Any
> > suggestions?  Perhaps there is a function that can be used to convert a
> > classpath element to a string value?? :-)
> >
> > Matt
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: classpath elements, properties, and interoperability

Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
<path id="some.path">
  .
  .
  .
</path>

<property "path.string" refid="some.path"/>

voila!  :)



----- Original Message -----
From: "Matt Coarr" <mc...@mitre.org>
To: <an...@jakarta.apache.org>
Sent: Friday, April 05, 2002 10:39 AM
Subject: classpath elements, properties, and interoperability


> Hello,
>
> I had been using a property to reference my classpath as a string value.
>  So this was being used with the javac task and with the exec and execon
> tasks (to call the ejbc command under the iplanet app server).
>
> Then I tried to switch over to using the classpath element -- it's more
> flexible, more readable, and just a better way to do it.  However I ran
> into a problem.  How do I pass a value from a classpath element to an
> external command or a task that isn't aware of classpath elements.  The
> javac task includes the classpathref that makes this easy, but using
> this value seems difficult/impossible with exec/execon.  Any
> suggestions?  Perhaps there is a function that can be used to convert a
> classpath element to a string value?? :-)
>
> Matt
>
>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>