Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-23 Thread Joerg Heinicke
On 23.03.2004 20:23, [EMAIL PROTECTED] wrote: stephan 2004/03/23 11:23:07 Modified:tools/src blocks-build.xsl Log: Allow to share codebase to other blocks. pathelement location=${{build.blocks}}/{$block-name}/mocks/ +pathelement

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-23 Thread Stephan Michels
Am Di, den 23.03.2004 schrieb Joerg Heinicke um 20:37: On 23.03.2004 20:23, [EMAIL PROTECTED] wrote: stephan 2004/03/23 11:23:07 Modified:tools/src blocks-build.xsl Log: Allow to share codebase to other blocks. pathelement

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-23 Thread Geoff Howard
Joerg Heinicke wrote: On 23.03.2004 20:23, [EMAIL PROTECTED] wrote: stephan 2004/03/23 11:23:07 Modified:tools/src blocks-build.xsl Log: Allow to share codebase to other blocks. pathelement location=${{build.blocks}}/{$block-name}/mocks/ +pathelement

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-23 Thread Joerg Heinicke
On 24.03.2004 01:53, Geoff Howard wrote: This was the reason for the common classpath, wasn't it? I wanted to have a look on it after having reverted the common classpath, but I guess that's no longer needed. Thanks for it. BTW, which block depends on other block's samples? Not sure if this

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-17 Thread Joerg Heinicke
On 17.03.2004 20:51, [EMAIL PROTECTED] wrote: cziegeler2004/03/17 11:51:14 Modified:tools/src blocks-build.xsl Log: Removed all antcalls - very fast build now (at least compared to the old system) Thanks, exactly this was the reason for the slow build. If you had not it already

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-12 Thread Stephan Michels
Am Fr, den 12.03.2004 schrieb Carsten Ziegeler um 08:25: Stephan Michels wrote Ehm, are you sure that this works? The xconf's from the different blocks have to be applied in the correct order (in the order of their dependencies). If you all apply at once this is imho not

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-12 Thread Carsten Ziegeler
Stephan Michels wrote: The patch method return a true if the patch was applied. So I retry to patch until there exists no patches to execute anymore. It's not perfect, but fulfil our needs. Ah, I see - and in the case of an error you avoid endless loops, I guess? Carsten

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-12 Thread Carsten Ziegeler
Stephan Michels wrote: The patch method return a true if the patch was applied. So I retry to patch until there exists no patches to execute anymore. It's not perfect, but fulfil our needs. Ah, I see - and in the case of an error you avoid endless loops, I guess? Yes

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-11 Thread Carsten Ziegeler
[EMAIL PROTECTED] wrote: Modified:tools/src blocks-build.xsl Log: Apply all xconf file in one shoot. Ehm, are you sure that this works? The xconf's from the different blocks have to be applied in the correct order (in the order of their dependencies). If you all apply at once

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-11 Thread Stephan Michels
Am Do, den 11.03.2004 schrieb Carsten Ziegeler um 16:48: [EMAIL PROTECTED] wrote: Modified:tools/src blocks-build.xsl Log: Apply all xconf file in one shoot. Ehm, are you sure that this works? The xconf's from the different blocks have to be applied in the correct order

RE: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-11 Thread Carsten Ziegeler
Stephan Michels wrote Ehm, are you sure that this works? The xconf's from the different blocks have to be applied in the correct order (in the order of their dependencies). If you all apply at once this is imho not guarenteed, right? Now it should work. I rewrote the XConfTask.

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-10 Thread Joerg Heinicke
On 10.03.2004 10:36, [EMAIL PROTECTED] wrote: Modified:tools/src blocks-build.xsl ... Using one classpath for all blocks instead of one classpath for each block. Any particular reason for this? I thought this was already in preparation of real blocks. Joerg

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2004-03-10 Thread Stephan Michels
Am Mi, den 10.03.2004 schrieb Joerg Heinicke um 12:41: On 10.03.2004 10:36, [EMAIL PROTECTED] wrote: Modified:tools/src blocks-build.xsl ... Using one classpath for all blocks instead of one classpath for each block. Any particular reason for this? I thought this was already

Re: cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2003-11-25 Thread Joerg Heinicke
Line 277 in blocks-build.xsl: target name=[EMAIL PROTECTED] unless=unless.exclude.block.{$block-name}/ Some else targets depend on this one. But what's the sense of it? Joerg

cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2003-07-18 Thread cziegeler
cziegeler2003/07/18 01:59:19 Modified:tools/src blocks-build.xsl Log: Allowing samples to have their own xconf patch: samplesxconf Revision ChangesPath 1.30 +7 -0 cocoon-2.1/tools/src/blocks-build.xsl Index: blocks-build.xsl

cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2003-07-18 Thread stephan
stephan 2003/07/18 02:46:24 Modified:tools/src blocks-build.xsl Log: Exclude files, which should be copied, instead to include some files types explicit. Revision ChangesPath 1.31 +13 -2 cocoon-2.1/tools/src/blocks-build.xsl Index: blocks-build.xsl

cvs commit: cocoon-2.1/tools/src blocks-build.xsl

2003-07-09 Thread bruno
bruno 2003/07/09 08:26:40 Modified:tools/src blocks-build.xsl Log: Use all javac parameters when building block test classes Revision ChangesPath 1.28 +7 -1 cocoon-2.1/tools/src/blocks-build.xsl Index: blocks-build.xsl