"Alexandre Maret" <[EMAIL PROTECTED]> wrote: [SNIPPED] > * Organizationnal Issues > > How can I stay up-to-date and have more or less the same dev-environment > as the main developpers have, so I do not start working on > soon-to-be-outdated-code (even though jetspeed's APIs are pretty > stable). > > There's code in the working-dogs CVS... but it is sometimes broken, so > how do you developpers work ? Right now, I have the choice between 3 > solutions: > - use 1.2b1 => a bit old > - use the CVS version => doesn't build "as is" (maybe I should checkout > tagged files ?) > - wait for 1.2b2 => I tend to avoid waiting for > unspecified/unspecifiable dates ;-) We just recently went live with our portal and what we had to do was settle on the last released version ( 1.2b1 ) for production. Then I just have the current code checked out of CVS to keep up-to-date and add new stuff. We also have development app servers to run the new stuff aside from our local boxes. You're right, CVS may be in a state of flux ( really bad right now, btw ). You can also get the nightly builds from a few days ago if you need to. Most of the time, CVS isn't broken for long. Subscribe to the jserv-dev list and you'll also get commit email to see what people are doing... jb Jeff Brekke mailto:[EMAIL PROTECTED] http://sites.netscape.net/ekkerbj ____________________________________________________________________ Get your own FREE, personal Netscape WebMail account today at http://home.netscape.com/webmail -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://java.apache.org/main/mail.html> Problems?: [EMAIL PROTECTED]
