RE: Re: new avalon/excalibur test release
> Joerg Heinicke wrote: > > > > > Yes, that should be the way to go. Furthermore (if it is > possible) you > > should add a dependency on the xmlutil issue to the Cocoon > issue, so > > that we get informed when xmlutil is fixed. > > Yes that sounds about right to me. Create the ticket and I'll > see to it > that it gets applied. > > OTOH, if you feel confident enough about the patch you can commit it > directly yourself, all Cocoon committers have write access to > excalibur/avalon svn. I am pretty confindent about the patch, but I have some problems getting my password resetted (long story..), so I cannot write yet...Anyway, I will create the issue in excalibur, try to set a dependency on the Cocoon issue, add a patch and hopefully see it ending up in cocoon. Regards Ard > > Cheers > Jorg > >
Re: new avalon/excalibur test release
Joerg Heinicke wrote: Yes, that should be the way to go. Furthermore (if it is possible) you should add a dependency on the xmlutil issue to the Cocoon issue, so that we get informed when xmlutil is fixed. Yes that sounds about right to me. Create the ticket and I'll see to it that it gets applied. OTOH, if you feel confident enough about the patch you can commit it directly yourself, all Cocoon committers have write access to excalibur/avalon svn. Cheers Jorg
Re: new avalon/excalibur test release
On 11.10.2006 11:41, Ard Schrijvers wrote: There is a cocoon jira issue outstanding (http://issues.apache.org/jira/browse/COCOON-1909) that is actually a excalibur-xmlutil flaw. It is about check-includes for stylesheets only working one level deep. I fixed this flaw in the XSLTProcessorImpl. I think many cocoon users would be glad to see this fix make it to the trunk. What is the way to go from here? Is it enough when I create a jira issue in excalibur components and then add a patch? Yes, that should be the way to go. Furthermore (if it is possible) you should add a dependency on the xmlutil issue to the Cocoon issue, so that we get informed when xmlutil is fixed. Jörg
RE: new avalon/excalibur test release
Hello Jorg, > Dear all, > > I have created a new test release of the avalon/excalibur components > here [1]. The aim of this release was to convert a/e to > maven2, so that > people could include it in their m2 based projects using proper > transitive dependency management based on clean poms. > > If you want to get involved in the testing process feel free > to give the > jars and poms a spin. Please send any feedback/comments to > the excalibur > dev list. If there are some jira issues outstanding that you > would like > to have addressed before the next release then please let us know so > this could still be considered. There is a cocoon jira issue outstanding (http://issues.apache.org/jira/browse/COCOON-1909) that is actually a excalibur-xmlutil flaw. It is about check-includes for stylesheets only working one level deep. I fixed this flaw in the XSLTProcessorImpl. I think many cocoon users would be glad to see this fix make it to the trunk. What is the way to go from here? Is it enough when I create a jira issue in excalibur components and then add a patch? Regards Ard Schrijvers > > @cocoon: i tested the ones we're using with core-webapp and > everything > seemed OK (at first sight). Perhaps some of the core-hackers could > provide more valuable feedback here. > > > Thanks > Jorg > > [1] > http://people.apache.org/repo/m2-snapshot-repository/excalibur -test-for-release/
new avalon/excalibur test release
Dear all, I have created a new test release of the avalon/excalibur components here [1]. The aim of this release was to convert a/e to maven2, so that people could include it in their m2 based projects using proper transitive dependency management based on clean poms. If you want to get involved in the testing process feel free to give the jars and poms a spin. Please send any feedback/comments to the excalibur dev list. If there are some jira issues outstanding that you would like to have addressed before the next release then please let us know so this could still be considered. @cocoon: i tested the ones we're using with core-webapp and everything seemed OK (at first sight). Perhaps some of the core-hackers could provide more valuable feedback here. Thanks Jorg [1] http://people.apache.org/repo/m2-snapshot-repository/excalibur-test-for-release/
