Classpath and style task

[Nicolas Mailhot <Ni...@one2team.com>]

Hi,

[Please CC me since I'm not subscribed to the list]

	I've been trying to add a style task to our ant
build process.
Much to my surprise, the style task doc states :

 « processor : name of the XSLT processor to use [...] The
first one found in your class path is the one that is used.
»

But there is no provision at all for specifying the
classpath, like in « javac ». 

I don't want to set up a specific system-wide classpath on
all our
stations just for « style » (and btw how am I supposed to
set up the classpath so Forte passes it to ant under Windows
?). More to the point, I don't want to rely on the users
classpath at all.

So could you please consider adding a nested « classpath »
element to the « style » one ? I'm really surprised no one
else asked for this before.

	Best regards,

-- 
Nicolas

Re: Classpath and style task

[Nicolas Mailhot <Ni...@one2team.com>]

On 2001.06.26 19:46 Jesse Glick wrote:
> Nicolas Mailhot wrote:

> So this seems to be implemented in dev builds now, good. I
> agree that 
> generally when a task needs some extra library, using
> <classpath> is 
> nicest. Of course when you use <taskdef> this comes for
> free, but for 
> "standard optional" tasks this is not possible. Hopefully
> Ant 2 will be 
> cleaner in this area.

That would be great

> BTW for Forte, best to ask on the Forte mailing lists or
> check its 
> online help, but in short: for optional.jar tasks, add any
> needed 
> additional JARs (xalan.jar, junit.jar, ...) to
> ${fortedir}/lib/ext/ and 
> restart.

Thanks for the tip,

-- 
Nicolas

Re: Classpath and style task

[Jesse Glick <Je...@netbeans.com>]

[a sort of old thread]

Nicolas Mailhot wrote:

> [snip]
>  « processor : name of the XSLT processor to use [...] The
> first one found in your class path is the one that is used.
> »
> 
> But there is no provision at all for specifying the
> classpath, like in « javac ». 
> 
> I don't want to set up a specific system-wide classpath on
> all our
> stations just for « style » (and btw how am I supposed to
> set up the classpath so Forte passes it to ant under Windows
> ?). More to the point, I don't want to rely on the users
> classpath at all.


So this seems to be implemented in dev builds now, good. I agree that 
generally when a task needs some extra library, using <classpath> is 
nicest. Of course when you use <taskdef> this comes for free, but for 
"standard optional" tasks this is not possible. Hopefully Ant 2 will be 
cleaner in this area.

BTW for Forte, best to ask on the Forte mailing lists or check its 
online help, but in short: for optional.jar tasks, add any needed 
additional JARs (xalan.jar, junit.jar, ...) to ${fortedir}/lib/ext/ and 
restart.

Cheers,
-Jesse

-- 
Jesse Glick   <ma...@netbeans.com>
NetBeans, Open APIs  <http://www.netbeans.org/>
tel (+4202) 3300-9161 Sun Micro x49161 Praha CR

Re: Classpath and style task

[Stefan Bodewig <bo...@apache.org>]

Nicolas Mailhot <Ni...@one2team.com> wrote:

> So could you please consider adding a nested « classpath »
> element to the « style » one ?

Yes, sounds reasonable.  Could you please make an enhancement reqeust
to our bug tracking system - this way we are sure that it won't get
lost.

Thanks

        Stefan