On Mon, 17 Dec 2001, Carsten Ziegeler wrote: > Gerhard Froehlich wrote: > > > > >-----Original Message----- > > >From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > >Sent: Monday, December 17, 2001 1:00 PM > > >To: Cocoon-Dev > > >Subject: Planning the next release (was Re: patch politics) > > > > > > > > >Hi Team, > > > > > >I think it's time to think of a new release which should be > > >a maintainance release. We have fixed some bugs, cleaned up > > >parts of the docs etc. > > > > > >Now, what else should be done? I see currently two points: > > > > > >a) The changing of the directory structure according to the proposal. > > > > I can do it if you want. But maybe I need some help: > > Proposal > > scratchpad/lib > > scratchpad/src/org/apache/cocoon/scratchpad/${packages} > > scratchpad/webapp/...?? > > > > I don't know if it is possible to have an extra cocoon.roles > > and cocoon.xconf file (Sitemap ?) for the scratchpad. That would > > be cool, to prevent messing up the production files. > > > Yes, it must be separated, so there must be separate roles and > configuration files. These all can be merged with a simple > (yet-to-be-written) > Ant task which merges during build all those files. For > the optional components this is already done with the sitemap, > so there should be no problem in extending this a little bit.
I don't think is it a big problem. If you'd like to compile the scratchpad part copy it over to the build directory which will overwrite the ones from the normal java directory (which include the .roles file. Same with the webapp dir. Giacomo > > Carsten > > >b) "Forgetting the 2.0 branch" to maintain only one CVS version. This > > > requires to move all experimental stuff into the scratchpad area. > > > We have to be sure to be compatible with 2.0! > > > > +1 > > > > >So what do you think about it? Perhaps a volunteer for a)? > > > > Gerhard > > > > "Whose cruel idea was it for the word "lisp" to have an "s" in it?" > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
