No one ever seems to reply to these messages.
The goals of Alexandria are admirable, but the tool as advertised has never
existed in any mature form. From the original Alexandria project there
emerged several proposals, the most successful of which seems to be the Gump
project. Most of what is available now through CVS is Gump related. There is
no active work happening on the 'Alexandria' project per se, although there
is work to try to resurrect some of its parts. See the attached email for
the most recent status.
You may also want to look into projects with similar goals:
Maven: http://jakarta.apache.org/maven/
Centipede: http://www.krysalis.org/index.shtml
-----Original Message-----
From: Amarish Khopkar [mailto:akhopkar@;captechventures.com]
Sent: Friday, October 18, 2002 10:02 AM
To: Alexandria Developers List; [EMAIL PROTECTED]
Subject: Trying to obtain Alexandria
Dear Developers,
I have had a chance to do research on your Alexandria project, and I must
say that it is an impressive tool. It appears to be a godsend to any open
source development environment aiming to maintain versioning, and
centralized source, javadoc and build control on a project basis. I find it
to be an ideal solution to our current deployment system, but have been
unable to obtain a working release of it.
Correct me if I'm wrong, but the alexandria-legacy.zip from the repository
appears to be outdated, and is throwing java.lang.VerifyErrors. And the one
that downloads from the "Use Alexandria" hyperlink of the alexandria
subproject doesn't appear to have an alexandria script and seems to be old.
In addition, it appears that every subproject except Alexandria appears to
have Release, Nightly builds, but Alexandria appears to have none of these.
I would really appreciate if you could guide me in obtaining a working
release of Alexandria.
Thank You.
Amarish
--- Begin Message ---
I've finished the first step of the Alexandria reworking.
In the alexandria module, you can now find the following projects:
- alexandria family (documentation):
- javasrc: java source code 2 html conversion with xrefs
- gump family (build)
- gump
- jenny (the xml descriptor merger)
- shrimpfactory (where the project descriptors are)
- bubba (descriptor editor)
- viprom (still in early stage, to access
the gump descriptor info from ant embed proposal)
STATUSES
- xsltdoc: it has been donated but uses Sun doclet code; needs someone
to take it and replace the sun classes (I don't have time ATM)
- Javasrc: works and is ready to be used.
- bubba: works but will need a DTD overview
- jenny: the buildfile builds the jenny.jar
- shrimpfactory: the buildfile can use jenny to create merge.xml
- viprom: unusable
- gump: eliminated the gen scripts, it now works like this:
- user runs ant in the gump dir
- it calls the buildfile in shrimpfactory
- which calls jenny
- and merges with -Dshrimpfactory.gump.descriptor=workspace2use
- it runs the stylesheets on the merge.xml
- the scripts are put in the gump bin dir
- user invokes the needed script from the gump build dir
In essence, make your profile in shrimpfactory, go in gump, run ant
-Dshrimpfactory.gump.descriptor=workspace2use, then ./bin/update.sh,
./bin/build.sh ...
Can we start thinking of finally ditching the proposal dir stuff?
We will need quite a few updates in the docs, etc, but let me know what
you think.
Thanks.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail:
<mailto:alexandria-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail:
<mailto:alexandria-dev-help@;jakarta.apache.org>
--- End Message ---
--
To unsubscribe, e-mail: <mailto:alexandria-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:alexandria-dev-help@;jakarta.apache.org>
