You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2005/10/19 10:51:51 UTC
Re: [jira] Commented: (FOR-675) upgrading commons-jxpath-1.2.jar
Ross Gardler wrote:
> Thorsten Scherler wrote:
> >David Crossley escribi??:
> >
> >>And it is
> >>preventing me working on real issues.
> >
> >Yeah, we should propose to drop the ns for the time this bug is being
> >fixed and go on with our work.
> >
> >+1
It is not so easy. Every user out there of 0.8-dev
would need to remove the namespace from their site.xml
I am hoping to find a way to automatically remove it
before forrest uses the file. Otherwise it will need
to be an upgrading_08 note.
> >Anyway, as soon as v2 is totally based on the lm, I will give it another
> >go. (hopefully then I have internet @home again)
>
> This issue is not affecting my current work directly, but if it is
> holding other devs up then I'm OK with this (it will affect me soon anyway).
My main problem is that it is causing general confusion.
It is very bad for community-building to have different
versions of whiteboard plugins and duplicated docs, etc.
-David
Re: [jira] Commented: (FOR-675) upgrading commons-jxpath-1.2.jar
Posted by David Crossley <cr...@apache.org>.
Thorsten Scherler wrote:
> David Crossley escribi??:
> > Ross Gardler wrote:
> > > Thorsten Scherler wrote:
> > > >David Crossley escribi??:
> > > >
> > > >>And it is
> > > >>preventing me working on real issues.
> > > >
> > > >Yeah, we should propose to drop the ns for the time this bug is being
> > > >fixed and go on with our work.
> > > >
> > > >+1
> >
> > It is not so easy. Every user out there of 0.8-dev
> > would need to remove the namespace from their site.xml
> >
> > I am hoping to find a way to automatically remove it
> > before forrest uses the file. Otherwise it will need
> > to be an upgrading_08 note.
>
> Actually that should not be so hard. We "only" have to use the
> strip_namespace.xsl when requesting the site.xml. I can do that if we
> want to do it. The plan is to add a preparation pipeline and change the
> lm to return this pipe (like cocoon://prepare.site.xml). I am using
> cocoon:// protocol in the lm-structurer.xml. It is working fine.
Hmmm, i thought that i had it working. After a final test
it wasn't. Would someone please look at the new stylesheet
main/webapp/resources/stylesheets/strip-default-namespace.xsl
Insert that transformer (or fix it if not correct) at
main/webapp/linkmap.xmap line 68 for "abs-linkmap"
main/webapp/menu.xmap line 65 for "abs-menulinks"
Replace "f:site" with "site" at
main/webapp/resources/stylesheets/site-to-book.xsl line 34
Replace lib/core/commons-jxpath-20030909.jar with commons-jxpath-1.2.jar
-David
> > > >Anyway, as soon as v2 is totally based on the lm, I will give it another
> > > >go. (hopefully then I have internet @home again)
> > >
> > > This issue is not affecting my current work directly, but if it is
> > > holding other devs up then I'm OK with this (it will affect me soon anyway).
> >
> > My main problem is that it is causing general confusion.
> > It is very bad for community-building to have different
> > versions of whiteboard plugins and duplicated docs, etc.
>
> agree
>
> salu2
> --
> thorsten
Re: [jira] Commented: (FOR-675) upgrading commons-jxpath-1.2.jar
Posted by Thorsten Scherler <th...@apache.org>.
El mié, 19-10-2005 a las 18:51 +1000, David Crossley escribió:
> Ross Gardler wrote:
> > Thorsten Scherler wrote:
> > >David Crossley escribi??:
> > >
> > >>And it is
> > >>preventing me working on real issues.
> > >
> > >Yeah, we should propose to drop the ns for the time this bug is being
> > >fixed and go on with our work.
> > >
> > >+1
>
> It is not so easy. Every user out there of 0.8-dev
> would need to remove the namespace from their site.xml
>
> I am hoping to find a way to automatically remove it
> before forrest uses the file. Otherwise it will need
> to be an upgrading_08 note.
Actually that should not be so hard. We "only" have to use the
strip_namespace.xsl when requesting the site.xml. I can do that if we
want to do it. The plan is to add a preparation pipeline and change the
lm to return this pipe (like cocoon://prepare.site.xml). I am using
cocoon:// protocol in the lm-structurer.xml. It is working fine.
>
> > >Anyway, as soon as v2 is totally based on the lm, I will give it another
> > >go. (hopefully then I have internet @home again)
> >
> > This issue is not affecting my current work directly, but if it is
> > holding other devs up then I'm OK with this (it will affect me soon anyway).
>
> My main problem is that it is causing general confusion.
> It is very bad for community-building to have different
> versions of whiteboard plugins and duplicated docs, etc.
agree
salu2
--
thorsten
"Together we stand, divided we fall!"
Hey you (Pink Floyd)