Return-Path: Delivered-To: apmail-forrest-user-archive@www.apache.org Received: (qmail 37396 invoked from network); 22 Jan 2007 17:23:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2007 17:23:46 -0000 Received: (qmail 13804 invoked by uid 500); 22 Jan 2007 17:23:52 -0000 Delivered-To: apmail-forrest-user-archive@forrest.apache.org Received: (qmail 13772 invoked by uid 500); 22 Jan 2007 17:23:52 -0000 Mailing-List: contact user-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@forrest.apache.org List-Id: Delivered-To: mailing list user@forrest.apache.org Delivered-To: moderator for user@forrest.apache.org Received: (qmail 41823 invoked by uid 99); 22 Jan 2007 15:24:13 -0000 X-ASF-Spam-Status: No, hits=2.3 required=10.0 tests=HTML_FONT_BIG,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of Don.Li@va.gov designates 152.130.26.46 as permitted sender) X-SBRS: None X-MID: 46985758 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAPNltEUKBhtc/2dsb2JhbAANgyE X-IronPort-AV: i="4.13,221,1167627600"; d="scan'208,217"; a="46985758:sNHT12358444581" Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C73E39.47B1EB7F" X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: Exception to "forrest clean" Date: Mon, 22 Jan 2007 10:23:33 -0500 Message-ID: <8DC8DEF96C43694491F475C5B8BFF4754C10D2@VANCRMSGA4.vha.med.va.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Exception to "forrest clean" Thread-Index: Acc+OUczGo74eG9eQEyJQ6WtrYxrog== From: "Li, Don" To: X-OriginalArrivalTime: 22 Jan 2007 15:23:35.0510 (UTC) FILETIME=[48948760:01C73E39] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C73E39.47B1EB7F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =20 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. Thorsten Scherler Sun, 21 Jan 2007 11:13:09 -0800 On Fri, 2007-01-19 at 16:23 -0500, Li, Don wrote: > I'm wondering if cocoon or ant supports a command like "keep", to keep > a directory and its associated files created by another app during > "forrest clean" process. >=20 =20 Out of the box no. Well let=B4s say yes it is because if we analyze the result of the command it should do NOTHING as I understand it. =20 If you want to develop such a task it should not be hard. You just need to specify better what should be deleted. =20 > =20 >=20 > >=20 > >=20 > =20 > description=3D"* Clean the project generated documents = directory"> >=20 > >=20 > >=20 > >=20 > =20 >=20 > =20 >=20 > =20 > description=3D"* Clean the project generated documents = directory"> >=20 > =20 Here you need to specify which dirs you want to delete. The delete command will act the following way. Imaging you have the "normal" FORREST build structure.=20 =20 I assume ${project.site-dir} is equivalent to build/site. Then you should not use this root if you have files/dirs in there that you want to keep. =20 >=20 > >=20 > =20 >=20 > >=20 > =20 >=20 > Is this approach doable?=20 =20 No, with my assumption not. =20 However why not: =20 =20 ----------------------- 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? =20 Question, forrest's projecthelp option indicates that doing forrest Or forrest site produces the same result, that is, to build a new site. however, in the forrest.xml file, I don't see any specification about = "site" (action), I see action(target) like "clean", "clean-site", "run" = etc. Does that mean everything else is for building a (new) site (for = "site" action)? =20 And before I do 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? =20 ------------------------ =20 =20 That should do want you want. Have a look at the ant manual. =20 ------------- Do key word search for "ant" did not produce any sort of meaning result = for its manual, where else could I dig (not to download the whole = package and then extract...)? --------- =20 Once again, many thanks. =20 =20 HTH =20 salu2 --=20 thorsten =20 "Together we stand, divided we fall!"=20 Hey you (Pink Floyd) =20 =20 ------_=_NextPart_001_01C73E39.47B1EB7F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

 

Thanks for the response.=A0 = Please see below.=A0 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.

Thorsten Scherler
Sun, 21 Jan 2007 11:13:09 -0800

On Fri, 2007-01-19 at 16:23 -0500, Li, Don =
wrote:
> =
I’m wondering if cocoon or ant supports a command like =
“keep”, to keep
> a =
directory and its associated files created by another app =
during
> =
“forrest clean” =
process.
> =
 
Out of =
the box no. Well let=B4s say yes it is because if we analyze =
the
result of =
the command it should do NOTHING as I understand =
it.
 
If you =
want to develop such a task it should not be hard. You just =
need
to =
specify better what should be =
deleted.
 
>=A0 =
> =
> =
<!-- Please note, I’m using the “clean” subset =
command, =
“clean-site”
> for =
demo and clarity sake=A0 -->
> =
> =
<!--=A0 as is -->
> =
> =
<target name=3D"clean-site" =
depends=3D"init-props"
> =
>=A0=A0=A0=A0=A0=A0 description=3D"* =
Clean the project generated documents =
directory">
> =
>=A0=A0=A0=A0 <delete =
failonerror=3D"false" =
dir=3D"${project.site-dir}"/>
=
> =
>=A0=A0=A0=A0 <delete =
failonerror=3D"false" =
file=3D"${project.brokenlinkfile}"/>
> =
>=A0 =
</target>
> =
>=A0 =
> =
> =
<!--=A0 to be or desirable state --> =
> =
> =
<target name=3D"clean-site" =
depends=3D"init-props"
> =
>=A0=A0=A0=A0=A0=A0 description=3D"* =
Clean the project generated documents =
directory">
> =
>=A0=A0=A0=A0 <delete =
failonerror=3D"false" =
dir=3D"${project.site-dir}"/>
=
 
Here you =
need to specify which dirs you want to delete. The =
delete
command =
will act the following way. Imaging you have the =
"normal"
FORREST =
build structure. 
 
I assume =
${project.site-dir} is equivalent to build/site. Then =
you
should =
not use this root if you have files/dirs in there that you =
want
to =
keep.
 
> =
>=A0=A0=A0=A0 <delete =
failonerror=3D"false" =
file=3D"${project.brokenlinkfile}"/>
> =
>=A0=A0=A0 <!-- NEW -- >=A0 =
> =
>=A0=A0=A0=A0 <keep =
failonerror=3D"false" =
dir=3D"${project.site-keep-dir}"/><=
/pre>
> =
 
Assuming =
the "keep" dir is a dir under build/site that cannot =
work
because =
you already have delete it in the step before using your =
given
example.
 
>=A0 =
> =
>=A0=A0 <!-- project.site-keep-dir is =
defined elsewhere in this xml =
file
> =
-->=A0 
> =
>=A0 =
</target>
> =
>=A0 =
> =
> Is =
this approach doable? 
 
No, with =
my assumption not.
 
However =
why not:
<target name=3D"clean-site-keep" =
depends=3D"init-props"
=A0=A0=A0=A0=A0 description=3D"copies =
the keep dir and clean the project =
generated
documents =
directory">
=A0=A0 =
<!-- NEW -- >=A0 
=A0=A0<!-- project.site-keep-dir-src =
and =
destination (des) is defined elsewhere in this xml file -->=A0 =
=A0=A0=A0=A0<copy =
failonerror=3D"false" =
dir=3D"${project.site-keep-dir-src}"
todir=3D"${project.site-keep-dir-des}&quo=
t;/>
=A0=A0=A0 =
<delete failonerror=3D"false" =
dir=3D"${project.site-dir}"/>
=
=A0=A0=A0 =
<delete failonerror=3D"false" =
file=3D"${project.brokenlinkfile}"/>
 =
</target>
 
-----------------------
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?
 
Question, =
forrest’s projecthelp option indicates that =
doing
forrest
Or
forrest =
site
produces =
the same result, that is, to build a new =
site.
however, =
in the forrest.xml file, I don’t see any specification about =
“site” (action), I see action(target) like =
“clean”, “clean-site”, “run” etc.=A0 =
Does that mean everything else is for building a (new) site (for =
“site” action)?
 
And =
before I do
=A0 =
<copy failonerror=3D"false" =
dir=3D"${project.site-keep-dir-src}"
todir=3D"${project.site-keep-dir-des}&quo=
t;/>
I would =
need to define both project.site-keep-dir-src and =
project.site-keep-dir-des.=A0 Would it suffice if I define them in this =
same forrest.build.xml file before running this =
command?
 
------------------------
 
 
That =
should do want you want. Have a look at the ant =
manual.
 
-------------
Do key = word search for “ant” did not produce any sort of meaning = result for its manual, where else could I dig (not to download the whole = package and then = extract…)?
---------
<=
font
size=3D2 face=3D"Courier New"> 
Once =
again, many thanks.
 
 
HTH
 
salu2
-- =
thorsten
 
"Together we stand, divided we =
fall!" 
Hey you =
(Pink Floyd)
 

 

------_=_NextPart_001_01C73E39.47B1EB7F--