You may also be interested in VPP (http://vpp.sourceforge.net). It provides
the following:
- VPPFilter, a FilterReader supporting VTL.
- VPP, an extenson of the Copy task integrating VPPFilter.
- VPPJavaC, an extension of the Javac task also integrating VPPFilter for
preprocessing .java files before compilation using VTL.
In addition to being able to use VTL, you also have access to all of your
Ant project properties via the key $ant. For example, you can get your
project's name with $ant.get("ant.project.name") in your templates.
In addition to the Anakia ant task, Velocity also supports Texen, a simple
ant task that launches Velocity using a 'control template'.
The current release of vpp is licensed under LGPL, but I will be moving the
next release to a BSD license soon.
didge
> -----Original Message-----
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 20, 2003 4:42 PM
> To: Ant Developers List
> Subject: Re: [PATCH] Velocity task
>
>
> On Monday, January 20, 2003, at 07:28 PM, Hiroaki Nakamura wrote:
> > No, the Velocity does not have Ant tasks.
>
> Just the Anakia ones, I guess. I'm kinda surprised there isn't more
> Ant integration with Velocity. I'm actually in the midst of doing a
> static blog site generation Ant task using Velocity (the generator will
> be pluggable, but Velocity is the primary templating engine I'm using
> now).
>
> > Well, I am not sure on this. I think it's OK that the velocity task is
> > distributed in either Ant or Velocity. But I wish this task to be
> > committed and released. I have been watching Velocity-dev ML
> > for a while, but there is still no release after velocity-1.3.1-rc2
> > (July 25, 2002), and proposed features seems to be neglected
> > after short discussions...
>
> *sigh* - While I can appreciate the effort it takes to do a final
> release of a Jakarta project (deep bow to Magesh!) I find that the
> Velocity/Turbine projects suffer more than other Jakarta projects and
> live in perpetual beta/RC state. Such a shame.
>
> > I just added this patch to Bugzilla, Ant's area.
> > Should I post this patch to Velocity-dev ML also? Opinions please >
> > all.
>
> Since Conor has picked this up, lets let him decide where he wants to
> go with it first. I'm happy to have it within Ant's codebase,
> personally.
>
> > As for XDoclet tags, I will look into it from now. Would you give me
> > a pointer of documentations I should read?
>
> First, just for fun, run the build in proposal/xdocs (be sure to have
> the latest from CVS). If you encounter problems, let me know. Then
> look at what it generates in the build directory. If your task is part
> of the binary of Ant you are running and in the Ant source tree on your
> local machine then you should see your task documentation generated.
> Check it for accuracy.
>
> Look at other Ant tasks in the Ant codebase and see the @tags on
> several of them. Eventually I'll document these tags more thoroughly
> than just referring to the source code, but that will give you an idea
> of whats going on. The goal is to have the XML generated be sufficient
> enough to generate Ant's task/datatype documentation eventually.
>
> Erik
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
