forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: Cocoon Ant Task
Date Mon, 13 Oct 2003 12:51:20 GMT
Stephan Michels wrote:

>On Mon, 13 Oct 2003, Upayavira wrote:
>
>  
>
>>I've just committed a Cocoon Ant task to Cocoon CVS, and would welcome
>>feedback on it.
>>
>>Notable points include:
>>1) The xconf is included within the build file, not referenced as a file
>>2) This task shares the same xconf parsing code with the CLI
>>(Main.java), which means that extensions to the bean only need be added
>>in one place.
>>3) There are no <node>value</node> entries, as Ant doesn't do variable
>>substitution on them
>>4) It runs Cocoon in the same process as Ant - it doesn't fork or
>>anything. If any such functionality is required, it can be added.
>>    
>>
>
>Great job.
>
Thanks.

>>        <cocoon verbose="true"
>>                classpathref="cp"
>>                follow-links="true"
>>                precompile-only="false"
>>                confirm-extensions="false"
>>                md5-compare="true"
>>                context-dir="${cocoon.context}"
>>                config-file="WEB-INF/cocoon.xconf"
>>                work-dir="build/work"
>>                dest-dir="build/dest"
>>                checksums-uri="build/work/checksums"
>>                default-filename="index.html"
>>                accept="*/*">
>>    
>>
>
>One question, can't you use System.getProperty("java.io.tmpdir")
>for your work directory? For example
>
>System.getProperty("java.io.tmpdir")+System.getProperty("file.separator")+"cocoon"
>
>So the user doesn't to worry about the work directory.
>  
>
I could do that if they don't provide one themselves, yes.

If that is considered a good idea, I can add it (it'll apply to both the 
CLI and the Task, which is exactly how it should be). I've added it to 
my todo list.

Regards, Upayavira



Mime
View raw message