Thank you, yesterday I did not take the top link (Ant Tasks) as Ant Functions/References when I was searching for the Copy command.
-----Original Message----- From: bill/wilandra [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 7:35 PM To: user@forrest.apache.org Subject: RE: Exception to "forrest clean" The Ant copy task is documented in the Ant manual (http://ant.apache.org/manual/CoreTasks/copy.html). Bill -----Original Message----- From: Li, Don [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 23, 2007 12:26 PM To: user@forrest.apache.org Subject: RE: Exception to "forrest clean" Ok. I think it's working now -- bug fixed (have verified that the directory and its associated files have all been copied to a newly generated site). Here's what I did. Defined the two {source} and {destination} variables with the forrest.properties file. Added the copy routine to the last action of the site.xml file and (doing a mkdir command for the {destination} directory prior to it, one may consider this as optional). Have left the forrest.build.xml alone. Now, "forrest clean" runs clean (no err msg etc.) "forrest site" has copied the directory and its associated files, other actions runs as usual ... Any documentation how all these pieces fit together like which piece is executed first and which one depends on which one? Though some are kind of obvious like site.xml is called or imported into the forrest.build.xml. Any good ant documentation out there? The ant Manual from the ant.apache.org does not seem to have a Reference section, particularly a command like copy. I figured out how it works by looking at how it is being used by the site.xml, not exactly the best way to go. Many thanks. -----Original Message----- From: Li, Don Sent: Monday, January 22, 2007 3:41 PM To: user@forrest.apache.org Subject: RE: Exception to "forrest clean" Many thanks. It seems that defining the two new directories of (source and destination) and issuing the copy command, all within the forrest.properties file failed to achieve what was intended, the CONOPS_files directory was not created, let alone its associated files. The following is added to the end of the forrest.properties file in my new project directory # fix the bug of failure to copy CONOPS_Files directory # define project.site-keep-dir-src project.site-keep-dir-src=src/documentation/CONOPS_files ## note, the above source directory and associated file DOES EXIST # create the directory under a new site <mkdir dir="${project.site-dir}/process/modeling/CONOPS_files"/> ## note, the above command may be optional? # define project.site-keep-dir-des <property name="project.site-keep-dir-des" location="${project.build-dir}/${project.site}/process/modeling/CONOPS_f iles"/> ## I'd like to try different ways to achieve the same thing, the above ## method to define a property is also acceptable, correct? <copy failonerror="false" dir="${project.site-keep-dir-src}" todir="${project.site-keep-dir-des}"/> Before I separate the definitions/property settings from target command I'd like to check with you first, the process runs for 45 minutes, I would hope next try would get what I want. Regards, -----Original Message----- From: Thorsten Scherler [mailto:[EMAIL PROTECTED] Sent: Monday, January 22, 2007 1:01 PM To: user@forrest.apache.org Subject: Re: Exception to "forrest clean" On Mon, 2007-01-22 at 10:23 -0500, Li, Don wrote: > > Thanks for the response. Please see below. Also, I have not > subscribed to the list yet, so, doing copy and paste for now, the > indent may not be obvious, sorry about that. hmm, I am moderator and need you to ask to subscribe since I may miss to moderate your mail and it will end up in the trash. Sad. It is hard to see what is from which author if you copy. Will try, but no guaranty I will find all your comments. > ... > ---------- > BY DL > How about this? > Add the copy command to the last action of "building a new site" hence least impact on the current process? Yeah why not. > > Question, forrest's projecthelp option indicates that doing forrest Or > forrest site produces the same result, yes, since default ant target is site. > that is, to build a new site. > however, in the forrest.xml file, I don't see any specification about "site" (action), forrest/trunk/main/targets$ grep site * -R ... site.xml: <target name="site" ... It is an imported target. However which forrest.xml are you talking about? > I see action(target) like "clean", "clean-site", "run" etc. Does that mean everything else is for building a (new) site (for "site" action)? No. Some are for building plugins, ... > > And before I do > <copy failonerror="false" dir="${project.site-keep-dir-src}" > todir="${project.site-keep-dir-des}"/> > I would need to define both project.site-keep-dir-src and project.site-keep-dir-des. Would it suffice if I define them in this same forrest.build.xml file before running this command? You can do this or define it in an ant properties file like forrest.properties. In a current customer project I import all forrest targets in a custom ant project and calling the site target with different entries points. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
