Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
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.
...
But: Making an intelligent default and promoting it instead of asking to set property would be even better!
What does an intelligent default look like?
Well there were two suggestions, above. Or you can suggest own.
(Currently a block is expected to be checked out to /cocoon/blocks/[core|supported|...]/trunk)
I check out my blocks into these directories, also if I'd do it manually.
I personally do not find this neither convinient nor intuitive. You do usually checkout cocoon/trunk into cocoon, right? Similarly I'd checkout some block's trunk into "blockname" dir.
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.
Does Ant support SVN checkouts?
Of course: http://ant.apache.org/manual/CoreTasks/exec.html
:)
Vadim
