----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: "Avalon Development" <[email protected]>
Sent: Friday, October 12, 2001 4:30 PM
Subject: Re: org.apache.cocoon.components.xpath.XPathProcessor dependancy in
XMLResourceBundle


> On Sat, 13 Oct 2001 07:59, 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).
>
> Works for me. That was actually proposed a months or so ago but as yet no
one
> has got around to doing it ;)
>
> > How do others feel about this?

+1

And if this move is ok, where should we move
> > it?
>
> org.apache.avalon.excalibur.xpath

+0 .... maybe org.apache.avalon.excalibur.xml ?

>
> seems reasonable. Anyone else have thoughts?
>
>
> --
> Cheers,
>
> Pete
>
> ----------------------------------------------
> Money is how people with no talent keep score.
> ----------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to