You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Henning P. Schmiedehausen" <hp...@intermeta.de> on 2003/07/24 09:46:11 UTC
Velocity 1.3 or 1.4 ?
Hi,
the last official release of Velocity is 1.3.1. There is also a 1.4
branch which I remember to have some significant internal changes.
Which one is the branch to send bug fixes for? If one wants to work on
the velocity source, which one is the way to go? Working on post-1.3.1
or on the 1.4 branch?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"You are being far too rational for this discussion."
--- Scott Robert Ladd in <3F...@coyotegulch.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
Re: Velocity 1.3 or 1.4 ?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Geir Magnusson Jr." <ge...@adeptra.com> writes:
>Ok - so this isn't bugs in the templates, as you originally suggested,
>but a problem loading from the classpath. That's certainly something
>we need to fix. Does anyone have a concrete example?
Right. Sorry, I wasn't clear here.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
Re: Velocity 1.3 or 1.4 ?
Posted by "Geir Magnusson Jr." <ge...@adeptra.com>.
On Tuesday, August 26, 2003, at 04:24 PM, Henning P. Schmiedehausen
wrote:
> "Geir Magnusson Jr." <ge...@optonline.net> writes:
>
>> On Monday, August 25, 2003, at 04:21 AM, Henning Schmiedehausen wrote:
>
>>> At least for the Maven Torque plugin I proposed a patch which moves
>>> the
>>> Velocity version back from 1.4-dev to 1.3.1, because the 1.4-dev
>>> engines
>>> showed bugs in the templates that the 1.3.1 does not have. So there
>>> might be some work necessary here.
>
>> What bugs?
>
> Building Turbine with Maven needs the maven-torque-plugin which
> generates templates for the peer classes using Torque-gen and
> ultimatively the texen task.
>
> With Velocity-1.4-dev as pulled from ibiblio:
>
[SNIP]
> BUILD FAILED
> File......
> file:/home/henning/.maven/plugins/maven-torque-plugin-3.2-SNAPSHOT/
> Element... torque-data-model
> Line...... 228
> Column.... 49
> Resource not found. For more information consult the velocity log, or
> invoke ant with the -debug flag.
> Total time: 14 seconds
> Finished at: Tue Aug 26 22:21:06 CEST 2003
>
> With Velocity 1.3.1:
> torque:om-generate:
> Using contextProperties file:
> /tmp/turbine/jakarta-turbine-2.3-rc2/project.properties
> [torque-data-model] Using classpath
> [torque-data-model] Generating to file
> /tmp/turbine/jakarta-turbine-2.3-rc2/target/src/
> report.turbine.om.generation
> log4j:WARN No appenders could be found for logger
> (org.apache.torque.engine.database.transform.XmlToAppData).
> log4j:WARN Please initialize the log4j system properly.
> BUILD SUCCESSFUL
> Total time: 18 seconds
> Finished at: Tue Aug 26 22:23:16 CEST 2003
>
> It seems that loading templates from the class path no longer works.
>
> Switching to velocity-1.3.1 fixed all my problems so I didn't look
> into this any further.
Ok - so this isn't bugs in the templates, as you originally suggested,
but a problem loading from the classpath. That's certainly something
we need to fix. Does anyone have a concrete example?
geir
--
Geir Magnusson Jr 203-956-2604(w)
Adeptra, Inc. 203-434-2093(m)
geirm@adeptra.com 203-247-1713(m)
Re: Velocity 1.3 or 1.4 ?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Geir Magnusson Jr." <ge...@optonline.net> writes:
>On Monday, August 25, 2003, at 04:21 AM, Henning Schmiedehausen wrote:
>> At least for the Maven Torque plugin I proposed a patch which moves the
>> Velocity version back from 1.4-dev to 1.3.1, because the 1.4-dev
>> engines
>> showed bugs in the templates that the 1.3.1 does not have. So there
>> might be some work necessary here.
>What bugs?
Building Turbine with Maven needs the maven-torque-plugin which
generates templates for the peer classes using Torque-gen and
ultimatively the texen task.
With Velocity-1.4-dev as pulled from ibiblio:
torque:om-generate:
Using contextProperties file: /tmp/turbine/jakarta-turbine-2.3-rc2/project.prope rties
[torque-data-model] Using classpath
[torque-data-model] Generating to file /tmp/turbine/jakarta-turbine-2.3-rc2/ target/src/report.turbine.om.generation
log4j:WARN No appenders could be found for logger (org.apache.torque.engine.data base.transform.XmlToAppData).
log4j:WARN Please initialize the log4j system properly.
BUILD FAILED
File...... file:/home/henning/.maven/plugins/maven-torque-plugin-3.2-SNAPSHOT/
Element... torque-data-model
Line...... 228
Column.... 49
Resource not found. For more information consult the velocity log, or invoke ant with the -debug flag.
Total time: 14 seconds
Finished at: Tue Aug 26 22:21:06 CEST 2003
With Velocity 1.3.1:
torque:om-generate:
Using contextProperties file: /tmp/turbine/jakarta-turbine-2.3-rc2/project.properties
[torque-data-model] Using classpath
[torque-data-model] Generating to file /tmp/turbine/jakarta-turbine-2.3-rc2/target/src/report.turbine.om.generation
log4j:WARN No appenders could be found for logger (org.apache.torque.engine.database.transform.XmlToAppData).
log4j:WARN Please initialize the log4j system properly.
BUILD SUCCESSFUL
Total time: 18 seconds
Finished at: Tue Aug 26 22:23:16 CEST 2003
It seems that loading templates from the class path no longer works.
Switching to velocity-1.3.1 fixed all my problems so I didn't look
into this any further.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
Re: Velocity 1.3 or 1.4 ?
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On Monday, August 25, 2003, at 04:21 AM, Henning Schmiedehausen wrote:
> At least for the Maven Torque plugin I proposed a patch which moves the
> Velocity version back from 1.4-dev to 1.3.1, because the 1.4-dev
> engines
> showed bugs in the templates that the 1.3.1 does not have. So there
> might be some work necessary here.
What bugs?
>
> Regards
> Henning
>
>
> On Sat, 2003-08-23 at 01:01, Daniel Rall wrote:
>> "Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
>>
>>> Hi,
>>>
>>> the last official release of Velocity is 1.3.1. There is also a 1.4
>>> branch which I remember to have some significant internal changes.
>>>
>>> Which one is the branch to send bug fixes for? If one wants to work
>>> on
>>> the velocity source, which one is the way to go? Working on
>>> post-1.3.1
>>> or on the 1.4 branch?
>>
>> 1.4 branch would be preferred.
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> "Dominate!! Dominate!! Eat your young and aggregate! I have grotty
> silicon!"
> -- AOL CD when played backwards (User Friendly - 200-10-15)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-956-2604(w)
Adeptra, Inc. 203-434-2093(m)
geirm@adeptra.com 203-247-1713(m)
Re: Velocity 1.3 or 1.4 ?
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
At least for the Maven Torque plugin I proposed a patch which moves the
Velocity version back from 1.4-dev to 1.3.1, because the 1.4-dev engines
showed bugs in the templates that the 1.3.1 does not have. So there
might be some work necessary here.
Regards
Henning
On Sat, 2003-08-23 at 01:01, Daniel Rall wrote:
> "Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
>
> > Hi,
> >
> > the last official release of Velocity is 1.3.1. There is also a 1.4
> > branch which I remember to have some significant internal changes.
> >
> > Which one is the branch to send bug fixes for? If one wants to work on
> > the velocity source, which one is the way to go? Working on post-1.3.1
> > or on the 1.4 branch?
>
> 1.4 branch would be preferred.
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
"Dominate!! Dominate!! Eat your young and aggregate! I have grotty silicon!"
-- AOL CD when played backwards (User Friendly - 200-10-15)
Re: Velocity 1.3 or 1.4 ?
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
> Hi,
>
> the last official release of Velocity is 1.3.1. There is also a 1.4
> branch which I remember to have some significant internal changes.
>
> Which one is the branch to send bug fixes for? If one wants to work on
> the velocity source, which one is the way to go? Working on post-1.3.1
> or on the 1.4 branch?
1.4 branch would be preferred.
--
Daniel Rall
Re: Velocity 1.3 or 1.4 ?
Posted by "Geir Magnusson Jr." <ge...@adeptra.com>.
On Thursday, July 24, 2003, at 03:46 AM, Henning P. Schmiedehausen
wrote:
> Hi,
>
> the last official release of Velocity is 1.3.1. There is also a 1.4
> branch which I remember to have some significant internal changes.
Right now, it's not a branch. That's what's next - we do a 1.4-rc, and
then move into 1.5
>
> Which one is the branch to send bug fixes for? If one wants to work on
> the velocity source, which one is the way to go? Working on post-1.3.1
> or on the 1.4 branch?
Well, both. If there are significant bugs that we want an immediate
fix for in 1.3.1, then we need to patch that and release a 1.3.2 (etc).
Otherwise, 1.4 as we want to do a solid release, and after that....
I'm always happy to backport fixes, so if it's too onerous to do for
all, the preferred is a patch for HEAD
geir
>
> Regards
> Henning
>
>
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> "You are being far too rational for this discussion."
> --- Scott Robert Ladd in <3F...@coyotegulch.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: velocity-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: velocity-dev-help@jakarta.apache.org
>
>
--
Geir Magnusson Jr 203-956-2604(w)
Adeptra, Inc. 203-434-2093(m)
geirm@adeptra.com 203-247-1713(m)