On Tuesday 29 October 2002 12:58, Carsten Ziegeler wrote: > Torsten Curdt wrote: > > guys I'd like to have some backup before I change what I have in mind.... > > > > 1. add a "status=stable/unstable" attribute to the projects in module.xml > > ok > > > 2. add per project jar and class dependencies to the module.xml > > ok > > > 4. all blocks start with cocoon- (for besser visibility in gump) > > ok > > > 5. move the scratchpad stuff into a scratchpad block. the > > scratchpad libs will > > go into the lib/optional dir. they will be copied into the webapp only if > > necessary > > ok > > > 6. I'd like to move also the documentation into a block (same or separate > > block for javadocs?) > > What? Do you mean all documentation into one block? Or do you mean a per > block documentation? We discussed this several times and it was always > voted against it - and I think we shouldn't touch the documentation > system right now because of the current discussion about using forrest > or not.
must have missed that one... ok > > 7. I'm not quite sure about this one: what about also having a > > cocoon-core-block.jar instead of handling it specially > > The core is not a block, so we should not call it a block. wasn't quite sure about this, too > > 8. the roles should go into a separate roles.jar since this needs > > to include > > the roles from the different blocks. > > Why this? Adding roles from within a block during build already works > and putting it into a separate roles.jar doesn't help. AFAICS it doesn't... the cocoon.jar is build before the blocks are build so it cannot work. I just moved precept into a block and noticed the xroles does not get included. If you just want to add a new block - you wouldn't have to rebuild the core but compile that block which will produce the block and update the roles.jar. > Please, (this is not targeted at you Torsten, it's just an information) > let's avoid trying to implement the great block concept proposed by > Stefano and Giacomo silently by adding here something and fixing there > something. We agreed to move it to 2.2. believe me I didn't wanted to did it right now ;-) but while moving the precept stuff I found it's really not in good shape right now. IMHO not even good enough for a 2.1 release... > I talked with Stefano the last two days about blocks (and more), > and guess what, he convinced me that blocks are really cool. We > refined the design he already proposed and cleaned out the wrinkles. curious to hear more! > We will start implementing blocks as soon as 2.1 is *out*. But not > any sooner. > We both agreed on that. then let's at least polish the current build system a little... -- Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
