turbine-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Age Mooy" <am...@home.nl>
Subject RE: How to change build.xml to use 2.2b?
Date Thu, 04 Oct 2001 11:51:57 GMT

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" <amooy@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 <jvanzyl@apache.org> wrote regarding
> > > Re: How to change build.xml to use 2.2b?:
> > >
> > >
> > > > On 10/4/01 1:01 AM, "Jason Grant" <jason.grant@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 <jason.grant@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


Mime
View raw message