You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by "Geir Magnusson Jr." <ge...@optonline.net> on 2001/11/08 09:29:06 UTC
Velocity v1.2-rc3
The final release candidate is on the site in the usual place.
It would be great if everyone could give it a try in the next 2 days - if
all goes well, and no one opposes, we'll make it final on Saturday...
geir
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety." - Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity v1.2-rc3
Posted by Christopher Elkins <ch...@apache.org>.
On Fri, Nov 09, 2001 at 04:35:29PM -0800, Peter Lynch wrote:
>
> 2. How do I get a hold on the org.apache.log.* classes?
http://jakarta.apache.org/avalon/logkit/index.html
--
Christopher Elkins
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: What is the difference between a macro and a template
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 11/11/01 12:02 AM, "Robert Edgar" <ro...@eeplace.com> wrote:
> Excuse me if these are dumb questions.
>
> I understand that a macro can be defined inline, and I also understand how
> it can be used to save typing for small code snippets OK but taking a step
> back and looking at a larger use of macro's I understand that a macro can
> contain anything a template can.
>
> So what difference is there between #parse'ing a template and calling a
> macro?
>
> I know macro can be loaded into a global library, is their some inherent or
> performance advantage to take a large template and turn it into a global
> macro if it is used frequently by many other templates? or are macro's just
> a convenience method but aren't really any different from a template?
There actually are a few differences.
The biggest is that the #macro() takes parameters. This is important
because I think it makes your templates more readable, and 'causal'.
Instead of hoping that the array in the template bar.vm is called
'$fooarray', as in
#set($fooarray = $myarray)
#parse( "bar.vm" )
By using a VM
#barmacro( $myarray )
It's definite what is going on.
There are also some other properties of VMs, such as private namespaces and
'local context', which you can't get with templates...
geir
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
You're going to end up getting pissed at your software
anyway, so you might as well not pay for it. Try Open Source.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
What is the difference between a macro and a template
Posted by Robert Edgar <ro...@eeplace.com>.
Excuse me if these are dumb questions.
I understand that a macro can be defined inline, and I also understand how
it can be used to save typing for small code snippets OK but taking a step
back and looking at a larger use of macro's I understand that a macro can
contain anything a template can.
So what difference is there between #parse'ing a template and calling a
macro?
I know macro can be loaded into a global library, is their some inherent or
performance advantage to take a large template and turn it into a global
macro if it is used frequently by many other templates? or are macro's just
a convenience method but aren't really any different from a template?
Rob
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Dynamic Nested Templates -Don't Agree that this is not what Velo is for
Posted by Robert Edgar <ro...@eeplace.com>.
Thanks Geir,
By fixed I think what I meant was, refering to your example below, that the
BODY template was a static reference.
I hadnt thought of using variables for templates names.
Also fixed in that the body template is one template whereas we might have 4
template that together constitute the body for pageX, I know you could just
use another template to aggregate those template but it just looked like
more and more files whereas the beauty of the XSLT approach is one single
file can aggregate templates for the body and also aggregate templates for
the leftnav, rightnav etc.
Also taking your example the frame page for us would just be another generic
template rather than specific to a page, with XSLT essentialy I can say "use
template1 and within template1 replace the leftnav with the content of tpl2,
tpl3 and tpl4"
and on the next call say "use template1 and within template1 replace the
leftnav with the content of tpl5, tpl6". Template assembly or aggregation
becomes very dynamic.
Velocity can do this AFAIK ... just wasnt obvious at first glance.... XSLT
is beautiful and easy to use, and the only reason we are now looking at
Velocity is that we are moving to using a caching technology and each page
will use Edge Side Includes(ESI) to generate the trully dynamic content and
the rest of the page is now static html templates so we want to use a system
to pregenerate these static html templates from a collection of
sub-templates retaining XSLT to be accessed by the ESI for generating
dynamic content on the fly.
Rob
-----Original Message-----
From: Geir Magnusson Jr. [mailto:geirm@optonline.net]
Sent: Sunday, November 11, 2001 10:59 AM
To: velocity-user@jakarta.apache.org
Subject: Re: Dynamic Nested Templates -Don't Agree that this is not what
Velo is for
On 11/10/01 9:05 PM, "Robert Edgar" <ro...@eeplace.com> wrote:
> Guys,
> Maybe I didn't explain myself clearly, my fault!
>
> No problem, anyway here is my "take" on things.
>
> I understand that Velocity is a templating engine, we are currently using
> XSL as our templating engine, I have a standard "template" which is a
large
> XSL stylesheet, actually I have several "standard" templates covering
> different sorts of pages that I have on my web site. Within a standard
> template I then load sub-templates to format different sections, so on my
> site home page I have the main page template and sub templates for a
section
> on latest news .
So far so good. This is the kind of thing you can do with #parse(), for
example.
>
> Now to me this is EXACTLY what velocity is about.
>
> The only issue I had here was that Velocity "seemed" to require a template
> to be fixed rather than dynamic in that although it can have nested
> templates,
What do you mean 'fixed'?
A common technique is to setup a 'frame' or 'layout' that positions the
parts of the page, such as the top, nav section, footer, and body, and then
you use references to setup all the parts.... Something like
<table>
<tr>
<td colspan=2>
#parse( $header )
</td>
</tr>
<tr>
<td>
#parse( $leftnav )
</td>
<td>
#parse( $body )
</td>
</tr>
<tr>
<td colspan=2>
#parse($footer)
</td>
</tr>
</table>
And then the servlet choose the $header, $leftnav, $body and $footer based
on user and current context of the app.
Just one approach among many...
> using the #parse directive, these are preset in the template
> whereas I wanted something dynamic in that a template will display a VAR
at
> a point in the template but I want the VAR to be the output of #parse some
> previous template.
#parse() can take references, so the actual thing can be chose independently
of the framing/layout tempalte
> AND
>
> After looking a bit father myself it "seems" to me my "standard" templates
> can be loaded as Velocity Macro's in the form of the global library.
Hm
> My
> understanding is that a Macro is called and is passed parameters which can
> be anything including the rendered output of another template. If that is
> the case that almost exactly matches an XSL call-template directive.
Sure. You can do something like
#set($templateoutput = "#parse($foo)")
#myvelocimacro( $templateoutput )
(note the " in the #set() )
> So .... correct me if I am wrong .... but to me this is exactly what Velo
> is about and it can do what I want...
Then switch as fast as you can :)
I like XSL but I think it's really challenging for the view layer :)
geir
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"Whoever would overthrow the liberty of a nation must begin by subduing the
freeness of speech." - Benjamin Franklin
--
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: Dynamic Nested Templates -Don't Agree that this is not what Velo
is for
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 11/10/01 9:05 PM, "Robert Edgar" <ro...@eeplace.com> wrote:
> Guys,
> Maybe I didn't explain myself clearly, my fault!
>
> No problem, anyway here is my "take" on things.
>
> I understand that Velocity is a templating engine, we are currently using
> XSL as our templating engine, I have a standard "template" which is a large
> XSL stylesheet, actually I have several "standard" templates covering
> different sorts of pages that I have on my web site. Within a standard
> template I then load sub-templates to format different sections, so on my
> site home page I have the main page template and sub templates for a section
> on latest news .
So far so good. This is the kind of thing you can do with #parse(), for
example.
>
> Now to me this is EXACTLY what velocity is about.
>
> The only issue I had here was that Velocity "seemed" to require a template
> to be fixed rather than dynamic in that although it can have nested
> templates,
What do you mean 'fixed'?
A common technique is to setup a 'frame' or 'layout' that positions the
parts of the page, such as the top, nav section, footer, and body, and then
you use references to setup all the parts.... Something like
<table>
<tr>
<td colspan=2>
#parse( $header )
</td>
</tr>
<tr>
<td>
#parse( $leftnav )
</td>
<td>
#parse( $body )
</td>
</tr>
<tr>
<td colspan=2>
#parse($footer)
</td>
</tr>
</table>
And then the servlet choose the $header, $leftnav, $body and $footer based
on user and current context of the app.
Just one approach among many...
> using the #parse directive, these are preset in the template
> whereas I wanted something dynamic in that a template will display a VAR at
> a point in the template but I want the VAR to be the output of #parse some
> previous template.
#parse() can take references, so the actual thing can be chose independently
of the framing/layout tempalte
> AND
>
> After looking a bit father myself it "seems" to me my "standard" templates
> can be loaded as Velocity Macro's in the form of the global library.
Hm
> My
> understanding is that a Macro is called and is passed parameters which can
> be anything including the rendered output of another template. If that is
> the case that almost exactly matches an XSL call-template directive.
Sure. You can do something like
#set($templateoutput = "#parse($foo)")
#myvelocimacro( $templateoutput )
(note the " in the #set() )
> So .... correct me if I am wrong .... but to me this is exactly what Velo
> is about and it can do what I want...
Then switch as fast as you can :)
I like XSL but I think it's really challenging for the view layer :)
geir
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"Whoever would overthrow the liberty of a nation must begin by subduing the
freeness of speech." - Benjamin Franklin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Dynamic Nested Templates -Don't Agree that this is not what Velo is for
Posted by Robert Edgar <ro...@eeplace.com>.
Guys,
Maybe I didn't explain myself clearly, my fault!
No problem, anyway here is my "take" on things.
I understand that Velocity is a templating engine, we are currently using
XSL as our templating engine, I have a standard "template" which is a large
XSL stylesheet, actually I have several "standard" templates covering
different sorts of pages that I have on my web site. Within a standard
template I then load sub-templates to format different sections, so on my
site home page I have the main page template and sub templates for a section
on latest news .
Now to me this is EXACTLY what velocity is about.
The only issue I had here was that Velocity "seemed" to require a template
to be fixed rather than dynamic in that although it can have nested
templates, using the #parse directive, these are preset in the template
whereas I wanted something dynamic in that a template will display a VAR at
a point in the template but I want the VAR to be the output of #parse some
previous template.
AND
After looking a bit father myself it "seems" to me my "standard" templates
can be loaded as Velocity Macro's in the form of the global library. My
understanding is that a Macro is called and is passed parameters which can
be anything including the rendered output of another template. If that is
the case that almost exactly matches an XSL call-template directive.
So .... correct me if I am wrong .... but to me this is exactly what Velo
is about and it can do what I want...
Rob
-----Original Message-----
From: Geir Magnusson Jr. [mailto:geirm@optonline.net]
Sent: Sunday, November 11, 2001 4:36 AM
To: velocity-user@jakarta.apache.org
Subject: Re: Dynamic Nested Templates
On 11/10/01 2:46 PM, "LS" <al...@yahoo.com> wrote:
> Robert, I think what you are looking for is a web development framework.
> Velocity,
> on the other hand, is a templating engine that happens to work very well
with
> web
> frameworks. Several web frameworks exist, and I can recommend Maverick as
a
> very
> small, simple, free, and usable way to wrap a framework around Velocity
pages.
> Turbine, also from the Jakarta project, performs this role, along with
doing a
> lot
> of other things.
>
> Geir et al, I wonder if it makes sense to write up a quick blurb on this
topic
> and
> put it somewhere visible, like Velocity FAQ?
That's a good idea. Will do.
>
> --- Robert Edgar <ro...@eeplace.com> wrote:
>> I am trying to convert existing pages that use xsl into Velocity.
>>
>> What I want to know is how to implment the following style in Velocity...
>>
>> <xsl:template match="/page">
>> <xsl:call-template name="stdPage">
>> <xsl:with-param name="SideBar">
>> <xsl:call-template name="SideBar"/>
>> </xsl:with-param>
>> <xsl:with-param name="panelC">
>> <xsl:call-template name="FeatureBoxes" />
>> </xsl:with-param>
>> <xsl:with-param name="panelR">
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="2"/>
>> </xsl:call-template>
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="3"/>
>> </xsl:call-template>
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="4"/>
>> </xsl:call-template>
>> </xsl:with-param>
>> </xsl:call-template>
>> </xsl:template>
>>
>> If it isn't obvious what I have is a global template which is a standard
>> page with a left,center and right columns which I will fill with the
>> contents of parsing other templates. ie I want to call a template and
pass
>> it a parameter which is the result of parsing another template.
>>
>> I cant see how this is done in Velocity.
>>
>>
>> Rob
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Find a job, post your resume.
> http://careers.yahoo.com
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
You're going to end up getting pissed at your software
anyway, so you might as well not pay for it. Try Open Source.
--
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: Dynamic Nested Templates
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 11/10/01 2:46 PM, "LS" <al...@yahoo.com> wrote:
> Robert, I think what you are looking for is a web development framework.
> Velocity,
> on the other hand, is a templating engine that happens to work very well with
> web
> frameworks. Several web frameworks exist, and I can recommend Maverick as a
> very
> small, simple, free, and usable way to wrap a framework around Velocity pages.
> Turbine, also from the Jakarta project, performs this role, along with doing a
> lot
> of other things.
>
> Geir et al, I wonder if it makes sense to write up a quick blurb on this topic
> and
> put it somewhere visible, like Velocity FAQ?
That's a good idea. Will do.
>
> --- Robert Edgar <ro...@eeplace.com> wrote:
>> I am trying to convert existing pages that use xsl into Velocity.
>>
>> What I want to know is how to implment the following style in Velocity...
>>
>> <xsl:template match="/page">
>> <xsl:call-template name="stdPage">
>> <xsl:with-param name="SideBar">
>> <xsl:call-template name="SideBar"/>
>> </xsl:with-param>
>> <xsl:with-param name="panelC">
>> <xsl:call-template name="FeatureBoxes" />
>> </xsl:with-param>
>> <xsl:with-param name="panelR">
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="2"/>
>> </xsl:call-template>
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="3"/>
>> </xsl:call-template>
>> <xsl:call-template name="banner125">
>> <xsl:with-param name="index" select="4"/>
>> </xsl:call-template>
>> </xsl:with-param>
>> </xsl:call-template>
>> </xsl:template>
>>
>> If it isn't obvious what I have is a global template which is a standard
>> page with a left,center and right columns which I will fill with the
>> contents of parsing other templates. ie I want to call a template and pass
>> it a parameter which is the result of parsing another template.
>>
>> I cant see how this is done in Velocity.
>>
>>
>> Rob
>>
>>
>> --
>> To unsubscribe, e-mail:
>> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
>> <ma...@jakarta.apache.org>
>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Find a job, post your resume.
> http://careers.yahoo.com
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
You're going to end up getting pissed at your software
anyway, so you might as well not pay for it. Try Open Source.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Dynamic Nested Templates
Posted by LS <al...@yahoo.com>.
Robert, I think what you are looking for is a web development framework. Velocity,
on the other hand, is a templating engine that happens to work very well with web
frameworks. Several web frameworks exist, and I can recommend Maverick as a very
small, simple, free, and usable way to wrap a framework around Velocity pages.
Turbine, also from the Jakarta project, performs this role, along with doing a lot
of other things.
Geir et al, I wonder if it makes sense to write up a quick blurb on this topic and
put it somewhere visible, like Velocity FAQ?
--- Robert Edgar <ro...@eeplace.com> wrote:
> I am trying to convert existing pages that use xsl into Velocity.
>
> What I want to know is how to implment the following style in Velocity...
>
> <xsl:template match="/page">
> <xsl:call-template name="stdPage">
> <xsl:with-param name="SideBar">
> <xsl:call-template name="SideBar"/>
> </xsl:with-param>
> <xsl:with-param name="panelC">
> <xsl:call-template name="FeatureBoxes" />
> </xsl:with-param>
> <xsl:with-param name="panelR">
> <xsl:call-template name="banner125">
> <xsl:with-param name="index" select="2"/>
> </xsl:call-template>
> <xsl:call-template name="banner125">
> <xsl:with-param name="index" select="3"/>
> </xsl:call-template>
> <xsl:call-template name="banner125">
> <xsl:with-param name="index" select="4"/>
> </xsl:call-template>
> </xsl:with-param>
> </xsl:call-template>
> </xsl:template>
>
> If it isn't obvious what I have is a global template which is a standard
> page with a left,center and right columns which I will fill with the
> contents of parsing other templates. ie I want to call a template and pass
> it a parameter which is the result of parsing another template.
>
> I cant see how this is done in Velocity.
>
>
> Rob
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Dynamic Nested Templates
Posted by Robert Edgar <ro...@eeplace.com>.
I am trying to convert existing pages that use xsl into Velocity.
What I want to know is how to implment the following style in Velocity...
<xsl:template match="/page">
<xsl:call-template name="stdPage">
<xsl:with-param name="SideBar">
<xsl:call-template name="SideBar"/>
</xsl:with-param>
<xsl:with-param name="panelC">
<xsl:call-template name="FeatureBoxes" />
</xsl:with-param>
<xsl:with-param name="panelR">
<xsl:call-template name="banner125">
<xsl:with-param name="index" select="2"/>
</xsl:call-template>
<xsl:call-template name="banner125">
<xsl:with-param name="index" select="3"/>
</xsl:call-template>
<xsl:call-template name="banner125">
<xsl:with-param name="index" select="4"/>
</xsl:call-template>
</xsl:with-param>
</xsl:call-template>
</xsl:template>
If it isn't obvious what I have is a global template which is a standard
page with a left,center and right columns which I will fill with the
contents of parsing other templates. ie I want to call a template and pass
it a parameter which is the result of parsing another template.
I cant see how this is done in Velocity.
Rob
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity v1.2-rc3
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 11/10/01 2:13 AM, "Peter Lynch" <pe...@mindspring.com> wrote:
> Ok, I admit I just skipped over your messages about the "build" changes
> stuff. Entirely my fault.
> I just grabbed it from the release builds and ran.
>
> I like your thought about making the dependency jar available. If that was
> there next to the other releases, I may have clued in ( err..it would have
> been harder for me to clue out :-) )
It's pretty clear that the docs have to improve here. The information is in
the developers guide, and that¹s ok for reference, but not a great place.
So I will add a file, something like
WHY_ARE_THERE_TWO_JARS.txt
And
INSTALL.txt
Into the root of the tree, and I hope that this helps solve it.
Sorry about the confusion.
geir
>
> Thanks,
>
> -Peter
>
> ----- Original Message -----
> From: "Geir Magnusson Jr." <ge...@optonline.net>
> To: <ve...@jakarta.apache.org>
> Sent: Friday, November 09, 2001 5:34 PM
> Subject: Re: Velocity v1.2-rc3
>
> <snip>
>
> Let me start by saying that
>
> 1) I did announce this more than once, as recently as yesterday or the day
> before :)
> 2) I put it in the README
>
> <snip>
>
> Anyhow, this is why rc3 is a rc rather than a release - things changed so we
> wanted to see what would go wrong for people - so I will try to
>
> 1) document it even better than the README
> 2) also include a second jar with dependencies for the 1.2 release, and then
> stop that with 1.3 (but leave the jar-dep target in the build :)
>
> Hope this helps.
>
> Geir
>
>
>>
>>
>>
>> ----- Original Message -----
>> From: "Geir Magnusson Jr." <ge...@optonline.net>
>> To: <ve...@jakarta.apache.org>
>> Sent: Thursday, November 08, 2001 12:29 AM
>> Subject: Velocity v1.2-rc3
>>
>>
>>> The final release candidate is on the site in the usual place.
>>>
>>> It would be great if everyone could give it a try in the next 2 days - if
>>> all goes well, and no one opposes, we'll make it final on Saturday...
>>>
>>> geir
>>>
>>> --
>>> Geir Magnusson Jr.
> geirm@optonline.net
>>> System and Software Consulting
>>> "They that can give up essential liberty to obtain a little temporary
>> safety
>>> deserve neither liberty nor safety." - Benjamin Franklin
>>>
>>>
>>>
>>> --
>>> 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>
>>
>
> --
> Geir Magnusson Jr. geirm@optonline.net
> System and Software Consulting
> You're going to end up getting pissed at your software
> anyway, so you might as well not pay for it. Try Open Source.
>
>
>
> --
> 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>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
"He who throws mud only loses ground." - Fat Albert
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity v1.2-rc3
Posted by Peter Lynch <pe...@mindspring.com>.
Ok, I admit I just skipped over your messages about the "build" changes
stuff. Entirely my fault.
I just grabbed it from the release builds and ran.
I like your thought about making the dependency jar available. If that was
there next to the other releases, I may have clued in ( err..it would have
been harder for me to clue out :-) )
Thanks,
-Peter
----- Original Message -----
From: "Geir Magnusson Jr." <ge...@optonline.net>
To: <ve...@jakarta.apache.org>
Sent: Friday, November 09, 2001 5:34 PM
Subject: Re: Velocity v1.2-rc3
<snip>
Let me start by saying that
1) I did announce this more than once, as recently as yesterday or the day
before :)
2) I put it in the README
<snip>
Anyhow, this is why rc3 is a rc rather than a release - things changed so we
wanted to see what would go wrong for people - so I will try to
1) document it even better than the README
2) also include a second jar with dependencies for the 1.2 release, and then
stop that with 1.3 (but leave the jar-dep target in the build :)
Hope this helps.
Geir
>
>
>
> ----- Original Message -----
> From: "Geir Magnusson Jr." <ge...@optonline.net>
> To: <ve...@jakarta.apache.org>
> Sent: Thursday, November 08, 2001 12:29 AM
> Subject: Velocity v1.2-rc3
>
>
>> The final release candidate is on the site in the usual place.
>>
>> It would be great if everyone could give it a try in the next 2 days - if
>> all goes well, and no one opposes, we'll make it final on Saturday...
>>
>> geir
>>
>> --
>> Geir Magnusson Jr.
geirm@optonline.net
>> System and Software Consulting
>> "They that can give up essential liberty to obtain a little temporary
> safety
>> deserve neither liberty nor safety." - Benjamin Franklin
>>
>>
>>
>> --
>> 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>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
You're going to end up getting pissed at your software
anyway, so you might as well not pay for it. Try Open Source.
--
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: Velocity v1.2-rc3
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 11/9/01 7:35 PM, "Peter Lynch" <pe...@mindspring.com> wrote:
> A few issues for me....
>
> I was using Nightly build of velocity 1.3 dev from October 28, 2001 no
> probs.
> Also RC2 worked no problem.
>
> Now I first see this with RC3:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/collections/ExtendedProperties
> at
> org.apache.velocity.runtime.configuration.Configuration.<init>(Configuration
> .java:182)
>
> So I then added commons-collections.jar to my webapp's lib dir. Thought I
> was home free until
> this:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/log/output/AbstractOutputTarget
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:120)
> at
> org.apache.velocity.runtime.log.LogManager.createLogSystem(LogManager.java:1
> 04)
> at
> org.apache.velocity.runtime.RuntimeInstance.initializeLogger(RuntimeInstance
> .java:468)
> at
> org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:259)
> at
> org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:169)
> at org.apache.velocity.app.Velocity.init(Velocity.java:123)
>
Let me start by saying that
1) I did announce this more than once, as recently as yesterday or the day
before :)
2) I put it in the README
>
> Questions
> 1. Removing deprecated classes between release candidates. Is this typical?
No. We would never remove deprecated classes. We didn't remove any
classes, but just stopped putting all the Extra Crap in the velocity.jar.
Velocity uses logkit as its default logger, as well as commons collections
for configuration - so previously, we would dump all the classes we needed
from logkit, oro and collections in the velocity jar.
This presented problems when a user wanted to use their own collections,
logkit or oro jars. So the new build.xml will not include non-Velocity
classes in the jar created by the default 'jar' target.
> 2. How do I get a hold on the org.apache.log.* classes? Or should I if I
> don't want that dependency?
The real solution : I am lazy to a fault, so I also like to use the
complete jar with the dependencies, so I left in a build target called
'jar-dep' that will build a complete velocity.jar as before. With it, you
don't need to go find collections or logkit (although I will point out that
you don't have to look any further than Velocity's build/lib directory :)
Anyhow, this is why rc3 is a rc rather than a release - things changed so we
wanted to see what would go wrong for people - so I will try to
1) document it even better than the README
2) also include a second jar with dependencies for the 1.2 release, and then
stop that with 1.3 (but leave the jar-dep target in the build :)
Hope this helps.
Geir
>
>
>
> ----- Original Message -----
> From: "Geir Magnusson Jr." <ge...@optonline.net>
> To: <ve...@jakarta.apache.org>
> Sent: Thursday, November 08, 2001 12:29 AM
> Subject: Velocity v1.2-rc3
>
>
>> The final release candidate is on the site in the usual place.
>>
>> It would be great if everyone could give it a try in the next 2 days - if
>> all goes well, and no one opposes, we'll make it final on Saturday...
>>
>> geir
>>
>> --
>> Geir Magnusson Jr. geirm@optonline.net
>> System and Software Consulting
>> "They that can give up essential liberty to obtain a little temporary
> safety
>> deserve neither liberty nor safety." - Benjamin Franklin
>>
>>
>>
>> --
>> 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>
>
--
Geir Magnusson Jr. geirm@optonline.net
System and Software Consulting
You're going to end up getting pissed at your software
anyway, so you might as well not pay for it. Try Open Source.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Velocity v1.2-rc3
Posted by Peter Lynch <pe...@mindspring.com>.
A few issues for me....
I was using Nightly build of velocity 1.3 dev from October 28, 2001 no
probs.
Also RC2 worked no problem.
Now I first see this with RC3:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/commons/collections/ExtendedProperties
at
org.apache.velocity.runtime.configuration.Configuration.<init>(Configuration
.java:182)
So I then added commons-collections.jar to my webapp's lib dir. Thought I
was home free until
this:
Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/log/output/AbstractOutputTarget
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at
org.apache.velocity.runtime.log.LogManager.createLogSystem(LogManager.java:1
04)
at
org.apache.velocity.runtime.RuntimeInstance.initializeLogger(RuntimeInstance
.java:468)
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java:259)
at
org.apache.velocity.runtime.RuntimeSingleton.init(RuntimeSingleton.java:169)
at org.apache.velocity.app.Velocity.init(Velocity.java:123)
Questions
1. Removing deprecated classes between release candidates. Is this typical?
2. How do I get a hold on the org.apache.log.* classes? Or should I if I
don't want that dependency?
----- Original Message -----
From: "Geir Magnusson Jr." <ge...@optonline.net>
To: <ve...@jakarta.apache.org>
Sent: Thursday, November 08, 2001 12:29 AM
Subject: Velocity v1.2-rc3
> The final release candidate is on the site in the usual place.
>
> It would be great if everyone could give it a try in the next 2 days - if
> all goes well, and no one opposes, we'll make it final on Saturday...
>
> geir
>
> --
> Geir Magnusson Jr. geirm@optonline.net
> System and Software Consulting
> "They that can give up essential liberty to obtain a little temporary
safety
> deserve neither liberty nor safety." - Benjamin Franklin
>
>
>
> --
> 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>