Return-Path: 
 <cocoon-dev-return-21457-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 26965 invoked by uid 500); 22 Jan 2002 16:00:03 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 26952 invoked from network); 22 Jan 2002 16:00:02 -0000
Message-ID: <001d01c1a35d$8a8ee0b0$670004c0@PC103>
Reply-To: "Nicola Ken Barozzi" <barozzi@nicolaken.com>
From: "Nicola Ken Barozzi" <barozzi@nicolaken.com>
To: <cocoon-dev@xml.apache.org>
References: <GMEBIBHGAOFGJCDPJANDIEOFDHAA.cziegeler@s-und-n.de>
Subject: Re: [PATCH] new build targets
Date: Tue, 22 Jan 2002 16:57:49 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

I've refactored the patch as proposed on this list.
Since a target uses JTidy, I've added a line to the scripts that copies it
with other support jars.
The patch has been submitted to Bugzilla in two files; I'm having problems
in creating a patch for build.* files, so I've sent a "normal" diff instead.
Here is a short description of the new capabilities it adds to the Cocoon
build system.

- interactive build -
Prompts the user with common build targets. In case of war installation, it
also asks for the destination dir.
The main target is in i-build.xml, and another new target is in build.xml
(installwar).
To run, at the prompt:  build.[bat|sh] -buildfile=i-build.xml

- scratchpad build -
Prompts the user with scratchpad build targets. It's just a POC, because the
schecoon build it calls now was not written to run called by another task.
The main target is in s-build.xml.
To run, at the prompt:  build.[bat|sh] -buildfile=s-build.xml

- try task -
A task to try out new tasks.The main target is in build.xml, while the tasks
to try are in try-build.xml.
To run, at the prompt:  build.[bat|sh] try -Dtry.task=[task to try]

- jtidy task -
Task to clean an html file with jTidy. I had to reprocess the DOM to
eliminate double attributes in the same tags, that
jTidy doesn't correct and Bugzilla has in its html. (I queried jTidy guys,
and they said that they will change code only when the new Tidy is out)
The java task file is in tools/src/JTidyTask.java.
To run, in the build use:

    <taskdef name="jtidy" classname="JTidyTask"
        classpath="${tools.dir}/anttasks"/>

    <jtidy src="${build.patchqueue}/bugzillapatchqueue.html"
           dest="${build.patchqueue}/bugzillapatchqueue.xhtml"
           log="${build.patchqueue}/bugzillapatchqueue.log"
           summary="true"
           warn="true"/>

 where
 src: source html
 dest: result
 log: jtidy warnings-errors-summary log
 summary: show summary info
 warn: show warnings

- patchqueue tasks -
Tasks to get pending patches from Bugzilla and perform actions with it.The
tasks are in try-build.xml.
To run, at the prompt:  build.[bat|sh] try -Dtry.task=[task to try]
These tasks are:
- prepare-patchqueue:   Gets pending patches from bugzilla and cleans html
- patchqueue-xml : Transforms bugzilla patches html into xml
- patchqueue-xdocs: Makes patches.xml for xdocs using bugzilla patches xml
- patchqueue: Creates a notification of the current patch queue to the
mailing list
- patchqueue-notify: Sends a notification of the current patch queue to the
mailing list

Each task depends on the previous.

--
Nicola Ken Barozzi                 xml-cocoon@nicolaken.com
These are the days of miracle and wonder...
          ...so don't cry baby, don't cry...
                                                  Paul Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org