Uhu? Berin? Anyone? Are these changes ok? Should we vote on these or I'll just go ahead and commit?
> -----Original Message----- > From: Neeme Praks [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 16, 2001 12:53 AM > To: [email protected] > Subject: RE: org.apache.cocoon.components.xpath.XPathProcessor > dependancy in XMLResourceBundle > > > So, as I understand from Berin (and others), we should then move > org.apache.cocoon.components.xpath package from Cocoon CVS to > org.apache.avalon.excalibur.xml.xpath package in Avalon CVS. Correct? > Everybody agrees? > > Then I would also move the i18n stuff back to Avalon. > The changes will affect three classes: > org/apache/cocoon/generation/HTMLGenerator.java > org/apache/cocoon/transformation/XIncludeTransformer.java > org/apache/cocoon/transformation/I18nTransformer.java > > I can commit the new packages into Avalon CVS, but I don't have > write access > to Cocoon CVS, so I would just send it the patches? (We would > need to update > the avalon-excalibur JAR file as well). > > How many people are there who are actively using the i18n support in > Cocoon2? Can we consider the XMLResourceBundle code stable enough to be > moved from the scratchpad to the "real" Avalon? > > Rgds, > Neeme > > > -----Original Message----- > > From: Berin Loritsch [mailto:[EMAIL PROTECTED] > > Sent: Friday, October 12, 2001 10:50 AM > > To: [email protected] > > Subject: Re: org.apache.cocoon.components.xpath.XPathProcessor > > dependancy in XMLResourceBundle > > > > > > 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? > > > > > > org.apache.avalon.excalibur.xml.xpath > > > > That way we can also have the following: > > > > org.apache.avalon.excalibur.xml.parser > > org.apache.avalon.excalibur.xml.transformer > > > > (This is the componentization of those specific pieces--not the > > pipeline specific > > things in Cocoon). This allows Avalon to use parsers that are > > not JAXP compliant > > and transformers that are not TRAX compliant. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
