You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Jason Grant <ja...@logular.com> on 2001/10/04 03:48:38 UTC
How to change build.xml to use 2.2b?
I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
required to my webapp build.xml, however there is no update in the
jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
about status of TDK in CVS - appears to be for turbine 3)
Problem description: When I invoke 'build init', I get the error shown
below, which suggests that the ant task has changed.
BUILD FAILED
/usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
"databasename" attribute
It is complaining about the attribute indicated below, but removal of
this attribute from my build.xml creates more hassles.
<torque-create-db
controlTemplate="sql/db-init/Control.vm"
outputDirectory="${outputDirectory}/sql"
templatePath="${templatePath}"
outputFile="${script}"
targetPlatform="${platform}"
targetDatabase="${database}"
databaseName="${project}" <-------------this one
databaseUser="${databaseUser}"
databasePassword="${databasePassword}"
databaseHost="${databaseHost}"
/>
Thanks,
J.
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Bojan Smojver <bo...@binarix.com>.
Mircea Zahan wrote:
>
> No, I can't, I didn't write the Velocity classes :op
> And modifying the Velocity classes is not a sollution, if that's
> what you suggest.
>
> Velocity generates the header, you can check that on the
> simplest example you got. Look at the source of the rendered page,
> in the browser.
OK, I admit, I was being a bit of a bastard in my reply ;-)
My point was that Velocity doesn't force you into any such thing -
Velocity can generate Visual Basic (apologies to everyone for using rude
words :-) program code for all it cares about the output. So, if you
could show a bit of code and explain how your app works, that would
really help.
Personally, I use Velocity to serve XHTML. It takes the document from
the file, parses it into AST (I think :-) and during the merge inserts
the values into the resulting document. What's the meat of the document
is totally irrelevant.
I just created this document in one of my applications (named code.vm):
------------------------------------------
This is a totally bogus document $res.encodeURL($req.getRequestURI()).
------------------------------------------
and this is what the browser serves:
------------------------------------------
This is a totally bogus document /code.vm.
------------------------------------------
There are no headers at all...
Bojan
Re: How can I get rid of !DOCTYPE HTML ... header generatedbyVelocity?
Posted by Mircea Zahan <mz...@level7.ro>.
Someone gave me the link bellow. I browsed it and read the doc. I got many things cleared out indeed.
The only one I need to share with you is: you also need to (re)read that doc. With emphasis on "politeness".
http://www.tuxedo.org/~esr/faqs/smart-questions.html
You might be an old one on this mailing list, but that doesn't give you any right to be rude ...
... even if your name is Jon.
Cheers, Jon.
Mircea.
----- Original Message -----
From: "Jon Stevens" <jo...@latchkey.com>
To: "velocity-user" <ve...@jakarta.apache.org>
Sent: Thursday, October 04, 2001 8:39 PM
Subject: Re: How can I get rid of !DOCTYPE HTML ... header generatedbyVelocity?
> on 10/4/01 7:17 AM, "Attila Szegedi" <sz...@freemail.hu> wrote:
>
> > (Folks, don't we want to add a link to this to the Jakarta mailing lists
> > page?)
> >
> > Attila.
>
> Clearly my cvs commit message rings true...
>
> <http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/mail.xml?rev=1.1
> 9&content-type=text/vnd.viewcvs-markup>
>
>
>
> Needless to say, I don't see how someone can come here and imply something
> totally off the wall that they could have simply grep'ed the source code
> for, have someone tell them that it isn't true and then come back and have
> the gall to question that answer by saying:
>
> "Velocity generates the header, you can check that on the
> simplest example you got. Look at the source of the rendered page,
> in the browser."
>
> ...and not be called on it...
>
> -jon
Re: How can I get rid of !DOCTYPE HTML ... header generatedbyVelocity?
Posted by Attila Szegedi <sz...@freemail.hu>.
Hm. I must be suffering from selective blindness...
Attila.
----- Original Message -----
From: "Jon Stevens" <jo...@latchkey.com>
To: "velocity-user" <ve...@jakarta.apache.org>
Sent: 2001. október 4. 19:39
Subject: Re: How can I get rid of !DOCTYPE HTML ... header generatedbyVelocity?
> on 10/4/01 7:17 AM, "Attila Szegedi" <sz...@freemail.hu> wrote:
>
> > (Folks, don't we want to add a link to this to the Jakarta mailing lists
> > page?)
> >
> > Attila.
>
> Clearly my cvs commit message rings true...
>
> <http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/mail.xml?rev=1.1
> 9&content-type=text/vnd.viewcvs-markup>
>
>
<snip/>
>
> -jon
>
>
Re: How can I get rid of !DOCTYPE HTML ... header generated
byVelocity?
Posted by Jon Stevens <jo...@latchkey.com>.
on 10/4/01 7:17 AM, "Attila Szegedi" <sz...@freemail.hu> wrote:
> (Folks, don't we want to add a link to this to the Jakarta mailing lists
> page?)
>
> Attila.
Clearly my cvs commit message rings true...
<http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/mail.xml?rev=1.1
9&content-type=text/vnd.viewcvs-markup>
Needless to say, I don't see how someone can come here and imply something
totally off the wall that they could have simply grep'ed the source code
for, have someone tell them that it isn't true and then come back and have
the gall to question that answer by saying:
"Velocity generates the header, you can check that on the
simplest example you got. Look at the source of the rendered page,
in the browser."
...and not be called on it...
-jon
Re: How can I get rid of !DOCTYPE HTML ... header generated byVelocity?
Posted by Attila Szegedi <sz...@freemail.hu>.
Before your cynicism deepens, you really should read
http://www.tuxedo.org/~esr/faqs/smart-questions.html
(Folks, don't we want to add a link to this to the Jakarta mailing lists page?)
Attila.
----- Original Message -----
From: "Mircea Zahan" < >
To: <ve...@jakarta.apache.org>
Sent: 2001. október 4. 12:56
Subject: Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
> Ok, everybody, I was wrong, it is not the Velocity the one which generates the header.
>
> But, hey, no one was born with knowledge in the brain ... EXCEPT SOME.
>
> Anyway, I figured the problem, it is solved, but not thanx to your acid replies.
>
> "Thank you" and have lots of fun.
>
>
Re: How can I get rid of !DOCTYPE HTML ... header generated byVelocity?
Posted by Endre Stølsvik <En...@Stolsvik.com>.
On Thu, 4 Oct 2001, Mircea Zahan wrote:
|
| You're right, mea culpa.
|
| In fact the thing that pissed me off was Jon Stevens' reply.
Now, who DOESN'T get PISSED OFF by _anything_ Jon Stevens' says??
He's an asshole on mailinglists, and I've just joined Velocity! Which he
"owns".. Go Jon - Go Jon - Go JOOOONNNNNNNNNNNNNNNNNNN!!!!!
Apparently he's not that big a dick in real life. At least anybody that
knows him IRL says so. It's just that he hasn't read all those fine
"Netiquette" posts that he so frequently points to himself.
Like those sections saying something about "DON'T BE A FUCKING ASSHOLE
on a mailinglist", or "DON'T BE A FUCKING WIZ-SHIT on a mailinglist"..
But, hey, he's just one person. Put in a "Jon-Block" in your head, and
he'll go away..
Just for the record: Jon is apparently a very fine coder, he's just not a
very fine email-writer. So if you manage to fine-tune your Jon-Block to
let the essence of his mails reach your consciousness, you could actually
get some useful information out of his shit..
Mvh,
Endre.
Re: How can I get rid of !DOCTYPE HTML ... header generated byVelocity?
Posted by Mircea Zahan <mz...@level7.ro>.
You're right, mea culpa.
In fact the thing that pissed me off was Jon Stevens' reply.
So, I apologize to all the others and thank you for the effort.
I promise not to do it again,
Mircea.
> On 10/4/01 6:56 AM, "Mircea Zahan" <mz...@level7.ro> wrote:
>
> > Ok, everybody, I was wrong, it is not the Velocity the one which generates the
> > header.
> >
> > But, hey, no one was born with knowledge in the brain ... EXCEPT SOME.
> >
> > Anyway, I figured the problem, it is solved, but not thanx to your acid
> > replies.
> >
> > "Thank you" and have lots of fun.
>
>
> Hang on there. I don't think you are being fair.
>
> As I see it, the replies were trying to be helpful, for the most part.
>
> You made the strong statement :
>
> "Velocity generates the <!DOCTYPE HTML ....> header which tells IE
> to conform to the 4.0 standard.
>
> Is there any way I can convince Velocity not to generate it?"
>
> And Bojan said, only 33 minutes later,
>
> "Can you point to the code that does that?"
>
> (Which I thought fair, as you stated that 'Velocity generates...')
>
> You reply was something to the order of 'No, because I didn't write it, and
> I won't modify it.'
>
> Bojan then 'apologized' for being 'a bastard' (which wasn't the way I read
> it) and then proceeded to give you a helpful reply.
>
> So, think what you want, but remember that this is a volunteer group, and
> you have all the source code, and you did get your question answered :)
>
> 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
>
Re: How can I get rid of !DOCTYPE HTML ... header generated by
Velocity?
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 10/4/01 6:56 AM, "Mircea Zahan" <mz...@level7.ro> wrote:
> Ok, everybody, I was wrong, it is not the Velocity the one which generates the
> header.
>
> But, hey, no one was born with knowledge in the brain ... EXCEPT SOME.
>
> Anyway, I figured the problem, it is solved, but not thanx to your acid
> replies.
>
> "Thank you" and have lots of fun.
Hang on there. I don't think you are being fair.
As I see it, the replies were trying to be helpful, for the most part.
You made the strong statement :
"Velocity generates the <!DOCTYPE HTML ....> header which tells IE
to conform to the 4.0 standard.
Is there any way I can convince Velocity not to generate it?"
And Bojan said, only 33 minutes later,
"Can you point to the code that does that?"
(Which I thought fair, as you stated that 'Velocity generates...')
You reply was something to the order of 'No, because I didn't write it, and
I won't modify it.'
Bojan then 'apologized' for being 'a bastard' (which wasn't the way I read
it) and then proceeded to give you a helpful reply.
So, think what you want, but remember that this is a volunteer group, and
you have all the source code, and you did get your question answered :)
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
Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Mircea Zahan <mz...@level7.ro>.
Ok, everybody, I was wrong, it is not the Velocity the one which generates the header.
But, hey, no one was born with knowledge in the brain ... EXCEPT SOME.
Anyway, I figured the problem, it is solved, but not thanx to your acid replies.
"Thank you" and have lots of fun.
Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Attila Szegedi <sz...@freemail.hu>.
IE is the stupid here, as in some situations it generates the doctype declaration into the text returned by the "View Source" command. A good example is an empty HTTP response that ends up being
<!DOCTYPE ...>
<HTML>
<BODY>
</BODY>
</HTML>
or something similar.
To summarize: Velocity does not generate the header. IE adds it artificially in certain situations when it thinks the response is HTML.
Attila.
----- Original Message -----
From: "Mircea Zahan" <mz...@level7.ro>
To: <ve...@jakarta.apache.org>
Sent: 2001. október 4. 9:14
Subject: Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
> No, I can't, I didn't write the Velocity classes :op
> And modifying the Velocity classes is not a sollution, if that's
> what you suggest.
>
> Velocity generates the header, you can check that on the
> simplest example you got. Look at the source of the rendered page,
> in the browser.
>
>
Re: How can I get rid of !DOCTYPE HTML ... header generated by
Velocity?
Posted by "Geir Magnusson Jr." <ge...@optonline.net>.
On 10/4/01 3:14 AM, "Mircea Zahan" <mz...@level7.ro> wrote:
> No, I can't, I didn't write the Velocity classes :op
> And modifying the Velocity classes is not a sollution, if that's
> what you suggest.
>
> Velocity generates the header, you can check that on the
> simplest example you got. Look at the source of the rendered page,
> in the browser.
>
Just to join in the fun :
Velocity doesn't generate or add any output that wasn't either part of the
input template, or the data objects placed in the context and used in the
template.
It doesn't generate any headers, doesn't know about HTML, etc.
Period :)
Geir
> ----- Original Message -----
> From: "Bojan Smojver" <bo...@binarix.com>
> To: <ve...@jakarta.apache.org>
> Sent: Thursday, October 04, 2001 10:00 AM
> Subject: Re: How can I get rid of !DOCTYPE HTML ... header generated by
> Velocity?
>
>
>> Mircea Zahan wrote:
>>>
>>> Hello everybody.
>>>
>>> I need to build a site which needs only IE compatibility.
>>>
>>> So, I need that my generated HTML not to be by the HTML 4.0 standard,
>>> but to use IE's extensions.
>>>
>>> Velocity generates the <!DOCTYPE HTML ....> header which tells IE
>>> to conform to the 4.0 standard.
>>
>> Can you point to the code that does that?
>>
>> Bojan
>
--
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
Re: How can I get rid of !DOCTYPE HTML ... header generated by
Velocity?
Posted by Jon Stevens <jo...@latchkey.com>.
on 10/4/01 12:14 AM, "Mircea Zahan" <mz...@level7.ro> wrote:
> No, I can't, I didn't write the Velocity classes :op
> And modifying the Velocity classes is not a sollution, if that's
> what you suggest.
grep the source code and tell me where it generates this header.
> Velocity generates the header, you can check that on the
> simplest example you got. Look at the source of the rendered page,
> in the browser.
Don't be stupid. It isn't Velocity generating that header.
Geez...
-jon
Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Mircea Zahan <mz...@level7.ro>.
No, I can't, I didn't write the Velocity classes :op
And modifying the Velocity classes is not a sollution, if that's
what you suggest.
Velocity generates the header, you can check that on the
simplest example you got. Look at the source of the rendered page,
in the browser.
----- Original Message -----
From: "Bojan Smojver" <bo...@binarix.com>
To: <ve...@jakarta.apache.org>
Sent: Thursday, October 04, 2001 10:00 AM
Subject: Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
> Mircea Zahan wrote:
> >
> > Hello everybody.
> >
> > I need to build a site which needs only IE compatibility.
> >
> > So, I need that my generated HTML not to be by the HTML 4.0 standard,
> > but to use IE's extensions.
> >
> > Velocity generates the <!DOCTYPE HTML ....> header which tells IE
> > to conform to the 4.0 standard.
>
> Can you point to the code that does that?
>
> Bojan
Re: How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Bojan Smojver <bo...@binarix.com>.
Mircea Zahan wrote:
>
> Hello everybody.
>
> I need to build a site which needs only IE compatibility.
>
> So, I need that my generated HTML not to be by the HTML 4.0 standard,
> but to use IE's extensions.
>
> Velocity generates the <!DOCTYPE HTML ....> header which tells IE
> to conform to the 4.0 standard.
Can you point to the code that does that?
Bojan
How can I get rid of !DOCTYPE HTML ... header generated by Velocity?
Posted by Mircea Zahan <mz...@level7.ro>.
Hello everybody.
I need to build a site which needs only IE compatibility.
So, I need that my generated HTML not to be by the HTML 4.0 standard,
but to use IE's extensions.
Velocity generates the <!DOCTYPE HTML ....> header which tells IE
to conform to the 4.0 standard.
Is there any way I can convince Velocity not to generate it?
Thank you.
RE: How to change build.xml to use 2.2b?
Posted by Age Mooy <am...@home.nl>.
If you only JDIANJ and get the new torque templates, everything works. At least IWFFM
If your TRP was in the wrong location (ie not in the WEB-INF/conf dir) you didn't generate your app with 2.1
but with a beta of 2.1. This could also be the reason your build.xml file is not complete. In that case you're
working with a beta and basically YACOYO
Age
> -----Original Message-----
> From: Jason Grant [mailto:jason.grant@logular.com]
> Sent: Thursday, October 04, 2001 13:02
> To: turbine-user@jakarta.apache.org
> Subject: RE: How to change build.xml to use 2.2b?
>
>
> Thanks, but I think I'll wait until a build of TDK2.2 is available.
> Upgrading the templates was about the fifth thing I did after reading
> that getting 2.2b going was as simple as 'dropping a jar'.
>
> Here's my sorry tale:
>
> build 2.2b -> copy the jar -> find init task is broken -> upgrade build.xml -> upgrade templates -> revisit
> build.xml to fix contextPath for new location of turbine.props, project.props -> note changes to
> sql tasks &
> security target -> think may as well grab em -> update TR.props -> update build.properties -> grab
> security-related
> XML files -> grab DTDs -> ponder meaning of new database config items in TR.props -> attempt build
> -> find new
> tasks require code from new TDK (e.g. SQLExec) -> cannot find TDK2.2 binary -> try and build it
> myself -> realise
> it has tentacles -> check mailing list -> find build not recommended -> mail user group about
> broken build.xml &
> inability to just copy the jar -> told to just copy the jar... heh.
>
> BTW, you know how +1 and -1 have entered the apache vocab for expressing
> a vote? Perhaps we can also start to reuse the following standard
> shorthand for responses on this list, since I think they may find utility
> for quite a large range of queries:
>
> YACOYO="your are completely on your own"
> YACWYT="you are completely wasting your time"
> WEAYTTG="what exactly are you trying to gain"
> JDIANJ="just drop in a new jar"
> IWFFM="it works fine for me"
>
> J.
>
> <webcam depicts J grinning behind welding mask and asbestos suit>
>
>
>
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 10/4/01, 6:02:07 PM, "Age Mooy" <am...@home.nl> wrote regarding RE: How
> to change build.xml to use 2.2b?:
>
>
> > In your case, next to dropping the turbine 2.2 jar in the lib dir of your
> app, you also have to get the torque
> > templates from cvs and replace then ones in your app with them.
> > This because Jason removed the databaseName property and now uses the
> name property of the defined database
> > (which is "Default" if you don't specify it in the xml file I think)
>
> > Check out jakarta-turbine-2/conf/torque/templates and just copy that to
> the web-inf/build/bin/torque/templates
> > diretory and you're fine.
>
> > Age
>
> > > -----Original Message-----
> > > From: Jason Grant [mailto:jason.grant@logular.com]
> > > Sent: Thursday, October 04, 2001 08:00
> > > To: turbine-user@jakarta.apache.org
> > > Subject: Re: How to change build.xml to use 2.2b?
> > >
> > >
> > > WRT to wasting my time, simply dropping turbine-2.2b.jar into the lib
> > > directory doesn't work if I want to upgrade my database schema.
> > >
> > > As explained in my previous mail, 2.2b is incompatible with a 2.1
> > > build.xml (TorqueCreateDatabase has changed). Once I started to migrate
> > > build.xml to work with the 2.2 jar, I found that other upgrades had to
> > > follow (TR.props, torque templates, etc).
> > >
> > > This started for me because I was already running a 2.2b jar on top of
> > > peers/database generated from a 2.1 jar, but have a bug that I suspect is
> > > due to 2.1 peers running on top of turbine 2.2, and hence the attempt to
> > > generate my peers/database with 2.2.
> > >
> > > J.
> > >
> > >
> > > > "databasename" attribute
> > >
> > > > BUILD FAILED
> > >
> > > > /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > > > Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > > > "databasename" attribute
> > >
> > > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> > >
> > > On 10/4/01, 3:27:38 PM, Jason van Zyl <jv...@apache.org> wrote regarding
> > > Re: How to change build.xml to use 2.2b?:
> > >
> > >
> > > > On 10/4/01 1:01 AM, "Jason Grant" <ja...@logular.com> wrote:
> > >
> > > > > I found a build.xml in CVS, and attempted to manually migrate TR.props,
> > > > > torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
> > > > > I'm now at the stage where building my app fails because it cannot find
> > > > > org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
> > > > > TDK, but I cannot build it (and recall an email on this list saying not
> > > > > to bother - the build process is not for general consumption yet?).
> > >
> > > > Building the TDK is not for end users and never will be. If you want new
> > > > Turbine functionality than drop in a new JAR.
> > >
> > > > > Q: There doesn't appear to be a 2.2b TDK available for download. How
> > > > > should I progress from here, assuming that I need a 2.2b TDK to proceed?
> > >
> > > > You wait for the 2.2b1 TDK. If you need it now and can't wait you're
> > > > completely on your own.
> > >
> > > > > Having spent a number of hours on this, I suspect that an easier upgrade
> > > > > path may be to create the sample app from a 2.2b TDK, then strip it out
> > > > > and migrate my code across. It'd be good if there was a pre-built 2.2b
> > > > > TDK out there (assuming it's ready).
> > >
> > > > You are completely wasting your time. What exactly are you trying to
> > > gain?
> > > > If you want the latest Turbine than build it from CVS and drop it into
> > > your
> > > > WEB-INF/lib.
> > >
> > > > Tambora is a 2.1 application and I just use Turbine from the 2.x CVS and
> > > it
> > > > works fine.
> > >
> > > > > Thanks.
> > > > >
> > > > > J.
> > > > >
> > > > >>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> > > > >
> > > > > On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
> > > > > regarding How to change build.xml to use 2.2b?:
> > > > >
> > > > >
> > > > >> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
> > > > >> required to my webapp build.xml, however there is no update in the
> > > > >> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
> > > > >> about status of TDK in CVS - appears to be for turbine 3)
> > > > >
> > > > >> Problem description: When I invoke 'build init', I get the error shown
> > > > >> below, which suggests that the ant task has changed.
> > > > >
> > > > >> BUILD FAILED
> > > > >
> > > > >> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > > > >> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > > > >> "databasename" attribute
> > > > >
> > > > >
> > > > >> It is complaining about the attribute indicated below, but removal of
> > > > >> this attribute from my build.xml creates more hassles.
> > > > >
> > > > >> <torque-create-db
> > > > >> controlTemplate="sql/db-init/Control.vm"
> > > > >> outputDirectory="${outputDirectory}/sql"
> > > > >> templatePath="${templatePath}"
> > > > >> outputFile="${script}"
> > > > >> targetPlatform="${platform}"
> > > > >> targetDatabase="${database}"
> > > > >> databaseName="${project}" <-------------this one
> > > > >> databaseUser="${databaseUser}"
> > > > >> databasePassword="${databasePassword}"
> > > > >> databaseHost="${databaseHost}"
> > > > >> />
> > > > >
> > > > >
> > > > >
> > > > >> Thanks,
> > > > >
> > > > >> J.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >> ---------------------------------------------------------------------
> > > > >> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > > >> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > >
> > > > --
> > >
> > > > 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
> > >
> > >
> > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > >
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: How to change build.xml to use 2.2b?
Posted by Jason Grant <ja...@logular.com>.
Thanks, but I think I'll wait until a build of TDK2.2 is available.
Upgrading the templates was about the fifth thing I did after reading
that getting 2.2b going was as simple as 'dropping a jar'.
Here's my sorry tale:
build 2.2b -> copy the jar -> find init task is broken -> upgrade build.xml -> upgrade templates -> revisit
build.xml to fix contextPath for new location of turbine.props, project.props -> note changes to sql tasks &
security target -> think may as well grab em -> update TR.props -> update build.properties -> grab security-related
XML files -> grab DTDs -> ponder meaning of new database config items in TR.props -> attempt build -> find new
tasks require code from new TDK (e.g. SQLExec) -> cannot find TDK2.2 binary -> try and build it myself -> realise
it has tentacles -> check mailing list -> find build not recommended -> mail user group about broken build.xml &
inability to just copy the jar -> told to just copy the jar... heh.
BTW, you know how +1 and -1 have entered the apache vocab for expressing
a vote? Perhaps we can also start to reuse the following standard
shorthand for responses on this list, since I think they may find utility
for quite a large range of queries:
YACOYO="your are completely on your own"
YACWYT="you are completely wasting your time"
WEAYTTG="what exactly are you trying to gain"
JDIANJ="just drop in a new jar"
IWFFM="it works fine for me"
J.
<webcam depicts J grinning behind welding mask and asbestos suit>
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 10/4/01, 6:02:07 PM, "Age Mooy" <am...@home.nl> wrote regarding RE: How
to change build.xml to use 2.2b?:
> In your case, next to dropping the turbine 2.2 jar in the lib dir of your
app, you also have to get the torque
> templates from cvs and replace then ones in your app with them.
> This because Jason removed the databaseName property and now uses the
name property of the defined database
> (which is "Default" if you don't specify it in the xml file I think)
> Check out jakarta-turbine-2/conf/torque/templates and just copy that to
the web-inf/build/bin/torque/templates
> diretory and you're fine.
> Age
> > -----Original Message-----
> > From: Jason Grant [mailto:jason.grant@logular.com]
> > Sent: Thursday, October 04, 2001 08:00
> > To: turbine-user@jakarta.apache.org
> > Subject: Re: How to change build.xml to use 2.2b?
> >
> >
> > WRT to wasting my time, simply dropping turbine-2.2b.jar into the lib
> > directory doesn't work if I want to upgrade my database schema.
> >
> > As explained in my previous mail, 2.2b is incompatible with a 2.1
> > build.xml (TorqueCreateDatabase has changed). Once I started to migrate
> > build.xml to work with the 2.2 jar, I found that other upgrades had to
> > follow (TR.props, torque templates, etc).
> >
> > This started for me because I was already running a 2.2b jar on top of
> > peers/database generated from a 2.1 jar, but have a bug that I suspect is
> > due to 2.1 peers running on top of turbine 2.2, and hence the attempt to
> > generate my peers/database with 2.2.
> >
> > J.
> >
> >
> > > "databasename" attribute
> >
> > > BUILD FAILED
> >
> > > /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > > Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > > "databasename" attribute
> >
> > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> >
> > On 10/4/01, 3:27:38 PM, Jason van Zyl <jv...@apache.org> wrote regarding
> > Re: How to change build.xml to use 2.2b?:
> >
> >
> > > On 10/4/01 1:01 AM, "Jason Grant" <ja...@logular.com> wrote:
> >
> > > > I found a build.xml in CVS, and attempted to manually migrate TR.props,
> > > > torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
> > > > I'm now at the stage where building my app fails because it cannot find
> > > > org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
> > > > TDK, but I cannot build it (and recall an email on this list saying not
> > > > to bother - the build process is not for general consumption yet?).
> >
> > > Building the TDK is not for end users and never will be. If you want new
> > > Turbine functionality than drop in a new JAR.
> >
> > > > Q: There doesn't appear to be a 2.2b TDK available for download. How
> > > > should I progress from here, assuming that I need a 2.2b TDK to proceed?
> >
> > > You wait for the 2.2b1 TDK. If you need it now and can't wait you're
> > > completely on your own.
> >
> > > > Having spent a number of hours on this, I suspect that an easier upgrade
> > > > path may be to create the sample app from a 2.2b TDK, then strip it out
> > > > and migrate my code across. It'd be good if there was a pre-built 2.2b
> > > > TDK out there (assuming it's ready).
> >
> > > You are completely wasting your time. What exactly are you trying to
> > gain?
> > > If you want the latest Turbine than build it from CVS and drop it into
> > your
> > > WEB-INF/lib.
> >
> > > Tambora is a 2.1 application and I just use Turbine from the 2.x CVS and
> > it
> > > works fine.
> >
> > > > Thanks.
> > > >
> > > > J.
> > > >
> > > >>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> > > >
> > > > On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
> > > > regarding How to change build.xml to use 2.2b?:
> > > >
> > > >
> > > >> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
> > > >> required to my webapp build.xml, however there is no update in the
> > > >> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
> > > >> about status of TDK in CVS - appears to be for turbine 3)
> > > >
> > > >> Problem description: When I invoke 'build init', I get the error shown
> > > >> below, which suggests that the ant task has changed.
> > > >
> > > >> BUILD FAILED
> > > >
> > > >> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > > >> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > > >> "databasename" attribute
> > > >
> > > >
> > > >> It is complaining about the attribute indicated below, but removal of
> > > >> this attribute from my build.xml creates more hassles.
> > > >
> > > >> <torque-create-db
> > > >> controlTemplate="sql/db-init/Control.vm"
> > > >> outputDirectory="${outputDirectory}/sql"
> > > >> templatePath="${templatePath}"
> > > >> outputFile="${script}"
> > > >> targetPlatform="${platform}"
> > > >> targetDatabase="${database}"
> > > >> databaseName="${project}" <-------------this one
> > > >> databaseUser="${databaseUser}"
> > > >> databasePassword="${databasePassword}"
> > > >> databaseHost="${databaseHost}"
> > > >> />
> > > >
> > > >
> > > >
> > > >> Thanks,
> > > >
> > > >> J.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > >> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> > > --
> >
> > > 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
> >
> >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: How to change build.xml to use 2.2b?
Posted by Age Mooy <am...@home.nl>.
In your case, next to dropping the turbine 2.2 jar in the lib dir of your app, you also have to get the torque
templates from cvs and replace then ones in your app with them.
This because Jason removed the databaseName property and now uses the name property of the defined database
(which is "Default" if you don't specify it in the xml file I think)
Check out jakarta-turbine-2/conf/torque/templates and just copy that to the web-inf/build/bin/torque/templates
diretory and you're fine.
Age
> -----Original Message-----
> From: Jason Grant [mailto:jason.grant@logular.com]
> Sent: Thursday, October 04, 2001 08:00
> To: turbine-user@jakarta.apache.org
> Subject: Re: How to change build.xml to use 2.2b?
>
>
> WRT to wasting my time, simply dropping turbine-2.2b.jar into the lib
> directory doesn't work if I want to upgrade my database schema.
>
> As explained in my previous mail, 2.2b is incompatible with a 2.1
> build.xml (TorqueCreateDatabase has changed). Once I started to migrate
> build.xml to work with the 2.2 jar, I found that other upgrades had to
> follow (TR.props, torque templates, etc).
>
> This started for me because I was already running a 2.2b jar on top of
> peers/database generated from a 2.1 jar, but have a bug that I suspect is
> due to 2.1 peers running on top of turbine 2.2, and hence the attempt to
> generate my peers/database with 2.2.
>
> J.
>
>
> > "databasename" attribute
>
> > BUILD FAILED
>
> > /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > "databasename" attribute
>
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 10/4/01, 3:27:38 PM, Jason van Zyl <jv...@apache.org> wrote regarding
> Re: How to change build.xml to use 2.2b?:
>
>
> > On 10/4/01 1:01 AM, "Jason Grant" <ja...@logular.com> wrote:
>
> > > I found a build.xml in CVS, and attempted to manually migrate TR.props,
> > > torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
> > > I'm now at the stage where building my app fails because it cannot find
> > > org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
> > > TDK, but I cannot build it (and recall an email on this list saying not
> > > to bother - the build process is not for general consumption yet?).
>
> > Building the TDK is not for end users and never will be. If you want new
> > Turbine functionality than drop in a new JAR.
>
> > > Q: There doesn't appear to be a 2.2b TDK available for download. How
> > > should I progress from here, assuming that I need a 2.2b TDK to proceed?
>
> > You wait for the 2.2b1 TDK. If you need it now and can't wait you're
> > completely on your own.
>
> > > Having spent a number of hours on this, I suspect that an easier upgrade
> > > path may be to create the sample app from a 2.2b TDK, then strip it out
> > > and migrate my code across. It'd be good if there was a pre-built 2.2b
> > > TDK out there (assuming it's ready).
>
> > You are completely wasting your time. What exactly are you trying to
> gain?
> > If you want the latest Turbine than build it from CVS and drop it into
> your
> > WEB-INF/lib.
>
> > Tambora is a 2.1 application and I just use Turbine from the 2.x CVS and
> it
> > works fine.
>
> > > Thanks.
> > >
> > > J.
> > >
> > >>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> > >
> > > On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
> > > regarding How to change build.xml to use 2.2b?:
> > >
> > >
> > >> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
> > >> required to my webapp build.xml, however there is no update in the
> > >> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
> > >> about status of TDK in CVS - appears to be for turbine 3)
> > >
> > >> Problem description: When I invoke 'build init', I get the error shown
> > >> below, which suggests that the ant task has changed.
> > >
> > >> BUILD FAILED
> > >
> > >> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> > >> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> > >> "databasename" attribute
> > >
> > >
> > >> It is complaining about the attribute indicated below, but removal of
> > >> this attribute from my build.xml creates more hassles.
> > >
> > >> <torque-create-db
> > >> controlTemplate="sql/db-init/Control.vm"
> > >> outputDirectory="${outputDirectory}/sql"
> > >> templatePath="${templatePath}"
> > >> outputFile="${script}"
> > >> targetPlatform="${platform}"
> > >> targetDatabase="${database}"
> > >> databaseName="${project}" <-------------this one
> > >> databaseUser="${databaseUser}"
> > >> databasePassword="${databasePassword}"
> > >> databaseHost="${databaseHost}"
> > >> />
> > >
> > >
> > >
> > >> Thanks,
> > >
> > >> J.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > >> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> > --
>
> > 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
>
>
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: How to change build.xml to use 2.2b?
Posted by Jason Grant <ja...@logular.com>.
WRT to wasting my time, simply dropping turbine-2.2b.jar into the lib
directory doesn't work if I want to upgrade my database schema.
As explained in my previous mail, 2.2b is incompatible with a 2.1
build.xml (TorqueCreateDatabase has changed). Once I started to migrate
build.xml to work with the 2.2 jar, I found that other upgrades had to
follow (TR.props, torque templates, etc).
This started for me because I was already running a 2.2b jar on top of
peers/database generated from a 2.1 jar, but have a bug that I suspect is
due to 2.1 peers running on top of turbine 2.2, and hence the attempt to
generate my peers/database with 2.2.
J.
> "databasename" attribute
> BUILD FAILED
> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> "databasename" attribute
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 10/4/01, 3:27:38 PM, Jason van Zyl <jv...@apache.org> wrote regarding
Re: How to change build.xml to use 2.2b?:
> On 10/4/01 1:01 AM, "Jason Grant" <ja...@logular.com> wrote:
> > I found a build.xml in CVS, and attempted to manually migrate TR.props,
> > torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
> > I'm now at the stage where building my app fails because it cannot find
> > org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
> > TDK, but I cannot build it (and recall an email on this list saying not
> > to bother - the build process is not for general consumption yet?).
> Building the TDK is not for end users and never will be. If you want new
> Turbine functionality than drop in a new JAR.
> > Q: There doesn't appear to be a 2.2b TDK available for download. How
> > should I progress from here, assuming that I need a 2.2b TDK to proceed?
> You wait for the 2.2b1 TDK. If you need it now and can't wait you're
> completely on your own.
> > Having spent a number of hours on this, I suspect that an easier upgrade
> > path may be to create the sample app from a 2.2b TDK, then strip it out
> > and migrate my code across. It'd be good if there was a pre-built 2.2b
> > TDK out there (assuming it's ready).
> You are completely wasting your time. What exactly are you trying to
gain?
> If you want the latest Turbine than build it from CVS and drop it into
your
> WEB-INF/lib.
> Tambora is a 2.1 application and I just use Turbine from the 2.x CVS and
it
> works fine.
> > Thanks.
> >
> > J.
> >
> >>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> >
> > On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
> > regarding How to change build.xml to use 2.2b?:
> >
> >
> >> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
> >> required to my webapp build.xml, however there is no update in the
> >> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
> >> about status of TDK in CVS - appears to be for turbine 3)
> >
> >> Problem description: When I invoke 'build init', I get the error shown
> >> below, which suggests that the ant task has changed.
> >
> >> BUILD FAILED
> >
> >> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> >> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> >> "databasename" attribute
> >
> >
> >> It is complaining about the attribute indicated below, but removal of
> >> this attribute from my build.xml creates more hassles.
> >
> >> <torque-create-db
> >> controlTemplate="sql/db-init/Control.vm"
> >> outputDirectory="${outputDirectory}/sql"
> >> templatePath="${templatePath}"
> >> outputFile="${script}"
> >> targetPlatform="${platform}"
> >> targetDatabase="${database}"
> >> databaseName="${project}" <-------------this one
> >> databaseUser="${databaseUser}"
> >> databasePassword="${databasePassword}"
> >> databaseHost="${databaseHost}"
> >> />
> >
> >
> >
> >> Thanks,
> >
> >> J.
> >
> >
> >
> >
> >
> >
> >
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: turbine-user-help@jakarta.apache.org
> --
> 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
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: How to change build.xml to use 2.2b?
Posted by Jason van Zyl <jv...@apache.org>.
On 10/4/01 1:01 AM, "Jason Grant" <ja...@logular.com> wrote:
> I found a build.xml in CVS, and attempted to manually migrate TR.props,
> torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
> I'm now at the stage where building my app fails because it cannot find
> org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
> TDK, but I cannot build it (and recall an email on this list saying not
> to bother - the build process is not for general consumption yet?).
Building the TDK is not for end users and never will be. If you want new
Turbine functionality than drop in a new JAR.
> Q: There doesn't appear to be a 2.2b TDK available for download. How
> should I progress from here, assuming that I need a 2.2b TDK to proceed?
You wait for the 2.2b1 TDK. If you need it now and can't wait you're
completely on your own.
> Having spent a number of hours on this, I suspect that an easier upgrade
> path may be to create the sample app from a 2.2b TDK, then strip it out
> and migrate my code across. It'd be good if there was a pre-built 2.2b
> TDK out there (assuming it's ready).
You are completely wasting your time. What exactly are you trying to gain?
If you want the latest Turbine than build it from CVS and drop it into your
WEB-INF/lib.
Tambora is a 2.1 application and I just use Turbine from the 2.x CVS and it
works fine.
> Thanks.
>
> J.
>
>>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
> regarding How to change build.xml to use 2.2b?:
>
>
>> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
>> required to my webapp build.xml, however there is no update in the
>> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
>> about status of TDK in CVS - appears to be for turbine 3)
>
>> Problem description: When I invoke 'build init', I get the error shown
>> below, which suggests that the ant task has changed.
>
>> BUILD FAILED
>
>> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
>> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
>> "databasename" attribute
>
>
>> It is complaining about the attribute indicated below, but removal of
>> this attribute from my build.xml creates more hassles.
>
>> <torque-create-db
>> controlTemplate="sql/db-init/Control.vm"
>> outputDirectory="${outputDirectory}/sql"
>> templatePath="${templatePath}"
>> outputFile="${script}"
>> targetPlatform="${platform}"
>> targetDatabase="${database}"
>> databaseName="${project}" <-------------this one
>> databaseUser="${databaseUser}"
>> databasePassword="${databasePassword}"
>> databaseHost="${databaseHost}"
>> />
>
>
>
>> Thanks,
>
>> J.
>
>
>
>
>
>
>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: How to change build.xml to use 2.2b?
Posted by Jason Grant <ja...@logular.com>.
I found a build.xml in CVS, and attempted to manually migrate TR.props,
torque templates, DTDs, XML files, etc., to bring my 2.1 app up to 2.2b.
I'm now at the stage where building my app fails because it cannot find
org.apache.tdk.task.SQLExec. I assume that this is available in the 2.2b
TDK, but I cannot build it (and recall an email on this list saying not
to bother - the build process is not for general consumption yet?).
Q: There doesn't appear to be a 2.2b TDK available for download. How
should I progress from here, assuming that I need a 2.2b TDK to proceed?
Having spent a number of hours on this, I suspect that an easier upgrade
path may be to create the sample app from a 2.2b TDK, then strip it out
and migrate my code across. It'd be good if there was a pre-built 2.2b
TDK out there (assuming it's ready).
Thanks.
J.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 10/4/01, 11:48:38 AM, Jason Grant <ja...@logular.com> wrote
regarding How to change build.xml to use 2.2b?:
> I'm trying to migrate a 2.1 webapp to 2.2b. It looks like changes are
> required to my webapp build.xml, however there is no update in the
> jakarta-turbine-2 CVS. Can I pull one from the TDK CVS? (uncertain
> about status of TDK in CVS - appears to be for turbine 3)
> Problem description: When I invoke 'build init', I get the error shown
> below, which suggests that the ant task has changed.
> BUILD FAILED
> /usr/share/java/tdk-2.1/webapps/rwtransform/WEB-INF/build/build.xml:220:
> Class org.apache.turbine.torque.TorqueCreateDatabase doesn't support the
> "databasename" attribute
> It is complaining about the attribute indicated below, but removal of
> this attribute from my build.xml creates more hassles.
> <torque-create-db
> controlTemplate="sql/db-init/Control.vm"
> outputDirectory="${outputDirectory}/sql"
> templatePath="${templatePath}"
> outputFile="${script}"
> targetPlatform="${platform}"
> targetDatabase="${database}"
> databaseName="${project}" <-------------this one
> databaseUser="${databaseUser}"
> databasePassword="${databasePassword}"
> databaseHost="${databaseHost}"
> />
> Thanks,
> J.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org