I can't get the source from Avalon unless it is tagged the same as the cocoon jar. Otherwise there is no guarantee that it is what Cocoon is using. Was the source for the snapshot releases of the components used by Cocoon captured? or is there no way to reconstruct what 2.1.3 is built upon?
Ralph
I do not really understand your problem. If Cocoon has a versioned JAR (no date), then the Excalibur sources *are* tagged. Cocoon does not "invent" the versions. The name is not really the same, but you can easily look up the correct spelling using WinCVS or WebCVS. So for example http://cvs.apache.org/viewcvs.cgi/avalon-excalibur/component/src/java/org/apache/avalon/excalibur/component/AbstractDualLogEnabled.java shows a tag Avalon_Component_1_2_dev_mavenized, which is the one we are using at the moment.
Joerg
-----Original Message----- From: Joerg Heinicke [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2003 1:34 PM To: [EMAIL PROTECTED] Subject: Re: excalibur-sourceresolve
On 19.11.2003 19:31, Ralph Goers wrote:
It has nothing to do with ExcaliburTestCase except that it
is the same
problem. Cocoon ships with
excalibur-sourceresolve-1.0.2-dev as you said and
excalibur-component-1.2-dev. I can't find these at the
Avalon site. If they
are in Cocoon's CVS that would be sufficient and I'll get
it from there.
Check out avalon-excalibur CVS module. Then you can update the subdirectories by tags (released versions are tagged).
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
