> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Gary Lawrence Murphy > Sent: Monday, December 09, 2002 1:44 PM > To: Jetspeed Users List > Subject: Re: "ant tutorial-n" command > > > >>>>> "D" == David Sean Taylor <[EMAIL PROTECTED]> writes: > > D> This is how I develop my projects. I never mix my source trees > D> with Jetspeed's. > > If you have the time, I'd really like to see a short paper on > how you set this up because this is exactly my problem: I need to > follow the beta-release CVS but I need to develop an app for it > in parallel, and keep it in a different CVS. > > If this process is already covered in the tutorial then please ignore > this request ;) > np, yes it is covered. Throughout the intro, and in the See : http://www.bluesunrise.com/jetspeed-docs/JetspeedTutorial.htm#_Toc26987080
http://www.bluesunrise.com/jetspeed-docs/JetspeedTutorial.htm#_Toc26987002 This is one of the primary lessons in the tutorial: to give you a working example of a real project that can evolve and coexist outside the dev.cycle of the open source project. The deployment in Jetspeed is a nightmare. There is no equivalent of 'take a war for and drop it in the container'. (There will be future releases) I believe the process outlined in the tutorial will serve the purposes of teaching Jestpeed but also as a working example that you can easily tailor to your own project. Just take the build.xml, strip out all the tutorial stuff, and go with it. Better yet, another ant target: ant new-project Kind of like the TDK in Turbine. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
