Berin Loritsch wrote:
Stephen McConnell wrote:
Excalibur i18n
1. Does not need to be in the list.
Used by Pool. Unless you are saying there has been absolutely no change since it was last released.
Absolutely no change since the last release.
Ok.
Excalibur Component (ECM)
1. Excalibur component documentation (index.html link to JavaDoc points to the entire Avalon Javadoc - not the local component package javadoc). 2. Excalibur Component index.html describes TestCase and not ECM
Hmm. It is just title changing, or does it really describe TestCase?
Here is the sum total of the ECM documentation (excluding Javadoc).
Introduction
This project contains utilities which can be used to write Excalibur Test Cases.
Ok. This amounts to title changing. We can make the reference valid.
3. excalibur-component and excalibur-component-complete have identical extension names in their respective manifests (should be changed)
Ok. Do you know how to merge the extensions from all the other manifests automatically?
Yep. What exactly do you have in mind?
Well the JAR *technically* has several extensions in there. What I just did (CVS) is to change the extension name to "excalibur-component-complete" (same thing for Fortress). If this is enough, let's go with that. If not, we need to reflect all the extensions in the one manifest.
This is sufficient.
I think the assembly, meta and merlin jars are the only jars that actually include correct extension dependency declarations - doing this properly is something that would require review across all of Excalibur - and I don't think this is the time to do it.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
