Jason van Zyl wrote:
>
> Hi Guys,
>
> I would like to modify Texen so that it can resolve templates
> located in JARs.
>
> I am working on the TDK and I think it would be a lot cleaner if
> I could pull the torque templates from a JAR. This would make
> upgrading easier within the TDK and would also make it easier
> for projects like Scarab to upgrade torque without having to
> unpack the torque zip file.
>
> I would like to do the work this weekend and get the functionality
> into the TDK. So texen would allow a template path to be set, and
> or a JAR. I will also see what I can do for allowing multiple paths
> for ease of separation and multiple JARs so that people can contribute
> Texen tools in the form of an isolated JAR of templates.
>
wow.. you must have read my mind because I was going to ask about this
today. I would very much just like to drop a jar into the classpath and
be able to update at will.
I'd like to use Texen for two projects. One would be as a
quasi-configure type app using Ant. The CollabNet development
environment is pretty intricate and it can have quite a few different
options so being able to dynamically create build.xml and/or properties
files would be awesome.
For the second, Texen would be used to create rpm spec files as well as
meta files with different info about the rpms. I use Ant to create all
of our rpms and this would fit in nicely.
All of that being said, I'll be more than happy to help test and/or help
develop.
josh
