forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: destDir changes broke CLI (Re: CLI Feature request)
Date Sat, 27 Sep 2003 10:03:42 GMT
Jeff Turner wrote:

>On Fri, Sep 26, 2003 at 09:26:52AM +0100, Upayavira wrote:
>  
>
>>After some days during which my IDE wouldn't compile Cocoon, I have now 
>>committed this simple change.
>>
>>I have also reordered some code in the CLI, so that a destination 
>>directory specified on the command line will now override one specified 
>>in the xconf. All other command line parameters already override their 
>>xconf equivalents.
>>    
>>
>
>Ah, this has broken things somewhat.  Two problems:
>
>1) Using *only* the command-line param doesn't work.  Forrest's cli.xconf
>does not have a <dest-dir> entry, and instead relies on the --destDir
>param being passed in from the command-line.  Because of this I get:
>
>ERROR: You must specify a destination directory when defining a target
>  
>
I've just commented out my <dest-dir> and added --destDir build/dest  to 
the command line, and it has worked fine for me. Are you still having 
this problem?

>2) The first file to be rendered ends up in the <dest-dir> directory, not
>the overriding --destDir directory.  If the cli.xconf has:
>
>  <dest-dir>/tmp/wrong</dest-dir>
>
>At the end of the render, /tmp/wrong/ contains one file:
>
>drwxr-xr-x    2 jeff     jeff         1024 Sep 27 18:00 .
>drwxrwxrwt    9 root     root        14336 Sep 27 18:00 ..
>-rw-r--r--    1 jeff     jeff          766 Sep 27 18:00 favicon.ico
>
>favicon.ico happens to be the first to get rendered.  All the other files
>(excluding favicon.ico) end up in the --destDir directory.
>
>  
>
But you say this one doesn't exist, so I've ignored it.

Regards, Upayavira



Mime
View raw message