[PROPOSAL] Cactus deliverables

[Vincent Massol <vm...@octo.com>]

Hi,

With the new front ends (aka Petals) which are the the Ant one and the
Eclipse one, it seems no longer possible to deliver only a single zip
file as was done in the past.

Deliverables
------------

I would like to propose the following new deliverables (with these
names, where {API} = 12 or 13 and {version} = 1.5 for example):

* jakarta-cactus-petal-ant-{API}-{version}.zip
jakarta-cactus-petal-eclipse-{API}-{version}.zip (includes the Ant
Petal)

* jakarta-cactus-sample-servlet-{API}-{version}.zip (includes the Ant
Petal. Note: The Servlet Sample's goal is to demonstrate how to write
Cactus tests and how to use the Ant Petal).

* jakarta-cactus-doc-{version}.zip (Note: it is the exact copy of the
web site)

Note: The intent is that the end users will pick the Petal they want to
use and that Petal will contain everything needed to get them up and
running.

<future>
In the near future we could have:

* jakarta-cactus-petal-manual-{API}-{version}.zip (include the Cactus
jars + Cactus related jars only)

* jakarta-cactus-doc-{version}.pdf (The PDF version of the web site)
</future>

Build organization
------------------

Thus, I would like to propose:

* that each subproject (maybe excepted framework and anttasks) has a new
Ant target called "release" which produces the deliverables mentioned
above.

* that the main build.xml simply have a "release" target that delegates
to the subproject release targets.

* that the clover database be generated inside the documentation/
subproject (as it is used to produce documentation)

* that the website upload script be moved in the documentation
subproject build

Shall I go ahead?

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org