[jos-general] Release 1.0-33.5 of Release Frame is now availble.

[Gilbert C. H. II <gc...@mi...>]

"Release Frame" generates Ant scripts and RPM specifications. It is 
an x-framework, built upon XVCL Processor 
(http://fxvcl.sourceforge.net/) and XML Bind 
(http://cjos.sourceforge.net/html/CjosLibrary.html).

The XVCL Processor 2.07 (1h) is extended with the xmlproperty 
command. This command uses XML Bind to load and parse an XML document 
into a model, something borrowed from Christian Heller's book, 
"Cybernetics Oriented Programming (CYBOP) - An Investigation on the 
Applicability of Inter-Disciplinary Concepts" (Tux Tax). Many thanks 
Chrisian Heller!

The CjOS Project is switching to Release Frame for its upcoming 
release of CjOS 1.0-34.

Benefit. For the first time in a long time, I feel like I have caught 
up on my work. After designing and testing the Release Frame 
x-framework with the CjOS Project, I turned my attention to a much 
neglected project called RandDos. I saved much time and complexity by 
describing the jar to be distributed in distribution.xml and XVCL 
Processor writes all of the Ant scripts and RPM specifications for me.

How it works. The distribution.xml file contains the knowledge (what 
we want to release). The XVCL Processor uses an x-framework called 
"Release Frame" to read the distribution.xml document as a model and 
generate Ant scripts and RPM specifications. For each jar, there is a 
source edition, a binary edition, a no-source RPM and target RPMs 
(-ant, -javadoc and -websource).

In Karl Fogel's book, "Producing Open Source Software" (O'Reilly), he 
identifies the minimum requirements of a release. A product built by 
the "Release Frame" x-framework meets many of these requirements.

Thanks,