You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by Jason van Zyl <jv...@apache.org> on 2001/08/30 16:53:45 UTC

Texen

Hi,

I have made some changes to texen to allow generation from a set of
templates in the filesystem and from a JAR.

If a couple people could update their repositories and run the tests to make
sure everything is cool I would appreciate it.

Geir, I am going to try to get Torque working completely from a JAR, which I
think I can do now, so I'm pretty much finished with any changes I want to
make.

After 1.2 is release, I would like to move texen out of the velocity core,
either into a jakarta-velocity-texen repository or to the commons. I think
we should do the same with Anakia. My preference is for a
jakarta-velocity-${package} type setup for now.

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



Re: Texen

Posted by Daniel Rall <dl...@finemaltcoding.com>.
Jason van Zyl <jv...@apache.org> writes:

> At first I would prefer to keep it in jakarta-velocity-texen if no one is
> averse. I would consider moving texen to the commons but not now.

Texen in jakarta-velocity-texen currently makes the most sense to me
as well.

Re: Texen

Posted by Jason van Zyl <jv...@apache.org>.
On 8/30/01 12:11 PM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:

> On 8/30/01 11:46 AM, "Jason van Zyl" <jv...@apache.org> wrote:
> 
>> On 8/30/01 11:29 AM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:
>> 
>>> I think jakarta-velocity-texen is cool.  We can also consider if putting it
>>> in Commons makes sense, just to give it more exposure.  The reason I propose
>>> this is it would might help ease any of the political concerns people would
>>> have using Velocity, the evil JSP spoiler, whereas a Jakarta Commons  text
>>> processing tool is less frightening.
>>> 
>>> <shrug> :)
>> 
>> At first I would prefer to keep it in jakarta-velocity-texen if no one is
>> averse. I would consider moving texen to the commons but not now.
>> 
> 
> Why?
> 

I don't see any benefit of moving it to the commons, I don't think there is
necessarily any exposure or political benefits. Plus it's easier to move it
to jakarta-velocity-texen than put it in the sandbox and go through the
proposal process. Like I said I'm not averse to putting texen in the commons
eventually, but I would like to work on it in jakarta-velocity-texen first.
Who knows what it will become after it gets a serious cleanup.

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



Re: Texen

Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 8/30/01 11:46 AM, "Jason van Zyl" <jv...@apache.org> wrote:

> On 8/30/01 11:29 AM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:
> 
>> I think jakarta-velocity-texen is cool.  We can also consider if putting it
>> in Commons makes sense, just to give it more exposure.  The reason I propose
>> this is it would might help ease any of the political concerns people would
>> have using Velocity, the evil JSP spoiler, whereas a Jakarta Commons  text
>> processing tool is less frightening.
>> 
>> <shrug> :)
> 
> At first I would prefer to keep it in jakarta-velocity-texen if no one is
> averse. I would consider moving texen to the commons but not now.
> 

Why?



Re: Texen

Posted by Jason van Zyl <jv...@apache.org>.
On 8/30/01 11:29 AM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:

> I think jakarta-velocity-texen is cool.  We can also consider if putting it
> in Commons makes sense, just to give it more exposure.  The reason I propose
> this is it would might help ease any of the political concerns people would
> have using Velocity, the evil JSP spoiler, whereas a Jakarta Commons  text
> processing tool is less frightening.
> 
> <shrug> :)

At first I would prefer to keep it in jakarta-velocity-texen if no one is
averse. I would consider moving texen to the commons but not now.
 
> Geir
> 
> 

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



Re: Texen

Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 8/30/01 10:53 AM, "Jason van Zyl" <jv...@apache.org> wrote:

> Hi,
> 
> I have made some changes to texen to allow generation from a set of
> templates in the filesystem and from a JAR.
> 
> If a couple people could update their repositories and run the tests to make
> sure everything is cool I would appreciate it.

Things seem ok.  All tests pass for me, including the new texen-classpath

> 
> Geir, I am going to try to get Torque working completely from a JAR, which I
> think I can do now, so I'm pretty much finished with any changes I want to
> make.

Excellent
 
> After 1.2 is release, I would like to move texen out of the velocity core,
> either into a jakarta-velocity-texen repository or to the commons. I think
> we should do the same with Anakia. My preference is for a
> jakarta-velocity-${package} type setup for now.

I think it makes sense for texen, so texen can evolve and grow.   I am less
sure of anakia, just because it would be an inconvenience, and the easier
anakia is, the easier the battle will be.  I don't have strong feelings
though.

I think jakarta-velocity-texen is cool.  We can also consider if putting it
in Commons makes sense, just to give it more exposure.  The reason I propose
this is it would might help ease any of the political concerns people would
have using Velocity, the evil JSP spoiler, whereas a Jakarta Commons  text
processing tool is less frightening.

<shrug> :)

Geir