Vadim Gritsenko wrote:
Reinhard Poetz wrote:
The autentication-fw, session-fw, cron and html block can be found at
https://svn.apache.org/repos/asf/cocoon/blocks/supported/
You can check them out by
svn checkout blocks
I'm sorry, but this won't work - it's not sustainable in the long (and even short) term. You can't expect folks to checkout *all* versions, *all* branches, of *all* blocks. Some, probably, won't simply have enough hard disk space, or internet connection time!
Daniel's guess on checkout looks way more sane to me:
svn checkout https://.../cocoon/blocks/supported/authentication-fw/trunk \
authentication-fw
I'd suggest some naming convention in addition to this:
svn checkout https://.../cocoon/blocks/supported/authentication-fw/trunk \
cocoon-authentication-fw
But asking people to checkout .../cocoon/blocks is too much, IMHO.
Currently only 4 blocks have been moved, but in general, you're absolutly right. The block builder should work indepenently from where you check out your blocks.
(Currently the property blockbuilder.root would have to be set as commandline parameter. I'll add support for a system property too so that you don't have to type this path for every call :-) )
But: Making an intelligent default and promoting it instead of asking to set property would be even better!
In addition to this, ant target can be written which will checkout all of the blocks which are included into local.blocks.properties/blocks.properties into proper location and with proper naming convention, so that you won't even get chance to mess it up.
:-P
Vadim
