Hi Neeme,
Great to hear from you. :-)
Yes, the 'fork' of the XMLResourceBundle was mainly my doing -
it was intended to be a temporary solution until
XMLResourceBundle was officially a part of Avalon (ie. moved out
of the scratchpad).
I see no problems in moving it back to Avalon proper.
Cheers,
Marcus
On Fri, 12 Oct 2001, Neeme Praks wrote:
> hi again, fellow cocooners and avaloners! (long time, no see) :-)
>
> After being some time away from active development, I now started to look at
> the things that have happened with
> org.apache.avalon.excalibur.i18n.XMLResourceBundle while I was away.
> And discovered that there has happened a "fork" of the XMLResourceBundle
> from Avalon CVS tree to Cocoon CVS tree (org.apache.cocoon.i18n) together
> with some new additions and bugfixes.
>
> So, I started to look at the possibility to merge the Cocoon version of the
> XMLResourceBundle back to Avalon, and discovered that there is also one new
> dependancy introduced: org.apache.cocoon.i18n.XMLResourceBundle depends on
> org.apache.cocoon.components.xpath package.
>
> In order to still be able to merge the changes to Avalon, I would propose to
> move the org.apache.cocoon.components.xpath package also under Avalon (as it
> doesn't depend on any cocoon specific packages anyway).
>
> How do others feel about this? And if this move is ok, where should we move
> it?
>
> Rgds,
> Neeme
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: Managesoft GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&' Email : [EMAIL PROTECTED]
&&&&. Business Hours : +49 69 9757 200
&&&&&&&:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
