RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-16 Thread Stephan Michels
commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java On 12.03.2004 14:29, Stephan Michels wrote: In the orginal form of the blocks-build.xsl, we had separate targets for the patch files. But it was incredible slow. Then I merge these targets to one target, and rewrote

RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-16 Thread Carsten Ziegeler
: Saturday, March 13, 2004 3:03 PM To: [EMAIL PROTECTED] Subject: Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java On 12.03.2004 14:29, Stephan Michels wrote: In the orginal form of the blocks-build.xsl, we had separate targets for the patch files

RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-15 Thread Carsten Ziegeler
- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Saturday, March 13, 2004 3:03 PM To: [EMAIL PROTECTED] Subject: Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java On 12.03.2004 14:29, Stephan Michels wrote: In the orginal form of the blocks-build.xsl, we had

Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Joerg Heinicke
On 11.03.2004 16:11, [EMAIL PROTECTED] wrote: stephan 2004/03/11 07:11:10 Modified:tools/src/anttasks XConfToolTask.java Log: Retry to apply patches, which depends on each other. I really wonder why we re-implement the dependency resolving into a task (how simple it might be) when

Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Unico Hommes
Joerg Heinicke wrote: On 11.03.2004 16:11, [EMAIL PROTECTED] wrote: stephan 2004/03/11 07:11:10 Modified:tools/src/anttasks XConfToolTask.java Log: Retry to apply patches, which depends on each other. I really wonder why we re-implement the dependency resolving into a task (how

RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Carsten Ziegeler
Unico Hommes wrote: I thought that previously all xpatches for all blocks were executed in one go instead of separately and respecting dependency order. No, one patch after the other was applied previously. The order of the dependencies was used to define the order of the patches to be

Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Joerg Heinicke
On 12.03.2004 13:01, Carsten Ziegeler wrote: I thought that previously all xpatches for all blocks were executed in one go instead of separately and respecting dependency order. No, one patch after the other was applied previously. The order of the dependencies was used to define the order of

RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Carsten Ziegeler
Joerg Heinicke wrote: On 12.03.2004 13:01, Carsten Ziegeler wrote: I thought that previously all xpatches for all blocks were executed in one go instead of separately and respecting dependency order. No, one patch after the other was applied previously. The order of the

Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Unico Hommes
Carsten Ziegeler wrote: Joerg Heinicke wrote: On 12.03.2004 13:01, Carsten Ziegeler wrote: I thought that previously all xpatches for all blocks were executed in one go instead of separately and respecting dependency order. No, one patch after the other was

RE: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Carsten Ziegeler
Unico Hommes wrote: Now should the changes to XConfToolTask be rolled back? I think so, unless it has other advantages. Yes, it helps keeping the dependencies correct. Carsten

Re: cvs commit: cocoon-2.1/tools/src/anttasks XConfToolTask.java

2004-03-12 Thread Stephan Michels
Am Fr, den 12.03.2004 schrieb Joerg Heinicke um 13:30: On 12.03.2004 13:01, Carsten Ziegeler wrote: I thought that previously all xpatches for all blocks were executed in one go instead of separately and respecting dependency order. No, one patch after the other was applied