Le 30 mars 04, � 09:45, Gianugo Rabellino a �crit :
...(though what I'd really like to see is a more clean separation of stable/unstable blocks, possibly with a clear directory hierarchy (src/blocks/stable, src/blocks/unstable), a default commented out unstable.blocks.properties that Joe User *has* to read to compile such stuff and some more warning around...
Maybe just naming the block "scratchpad-javaflow" would do?
This would avoid the mess of adding yet more stuff to the current scratchpad block, yet make it very clear what's going on.
Well, actually my point is about user awareness. Today you just download Cocoon, read the docs, type ./build.sh and see some fast-scrolling messages muttering about unstable stuff, and that's it. I'm thinking of something more specific that forces the user to know what she's doing. A different property/target (./build.sh -Dinclude.unstable=true)? A different file to edit (local.unstable.block.properties)? Everything would do: but clearly a message that scrolls during the build is not enough.
Ciao,
-- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance - http://www.orixo.com (Blogging at: http://www.rabellino.it/blog/)
