You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Steven Noels <st...@outerthought.org> on 2002/03/01 09:51:55 UTC
migrating to the new DTD's
Hi,
I've been trying to get Forrest to use the new v1.1 version of the DTD's
yesterday, and found some strange behaviour in the entity resolver: if
you put a comment (--) at the end of the catalog file, Cocoon gets in an
endless loop of sorts.
Could anyone double-check so that we can post a bug to
Norman/cocoon-dev?
Next, I would like to know your opinion on the how & when to move to the
new DTD's. What I have been preparing for commit so far is the new
src/resources/schema directory, which has an extra import in it's
catalog file importing the old (Centipede) catalog until we have sorted
out how to fully isolate Centipede from Forrest in terms of DTD's,
catalogs and libraries (*if* we really want to do this for the sake of
Soc, but I'm +0 on that).
Other than that, I made sure that our own site xdocs are using public
identifiers pointing to the v1.1 versions (diff & new schema dir
attached).
Is this OK? Or should we fully isolate Forrest & Centipede from each
other?
With regards to my regular question on the unit of deployment that
Centipede should produce for Forrest: will we be re-using the cocoon
libs from Centipede for Forrest? Or will we put up a separate cocoon
config (xconf/xmap/etc) for the forrest.war...?
Regards,
</Steven>
RE: [PATCH] New fdoc build target (was Re: migrating to the new DTD's)
Posted by Steven Noels <st...@outerthought.org>.
Nicola wrote:
>
> Sorry, the patch is imcomplete. :-/ My fault.
>
> This one should work.
>
> You also need to do this after applying:
> 1. move jars from ./tools/cocoon/lib to ./lib/core, and
> remove placeholder
> file there
> 2. remove ./tools/cocoon dir entirely
> 3. remove from /tools/centipede/targets/docs.xtarget
>
Patch applied, please cross-check (and do your own patches in the future
;-)
Welcome!
</Steven>
Re: [PATCH] New fdoc build target (was Re: migrating to the new DTD's)
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
From: "Steven Noels" <st...@outerthought.org>
> Steven Noels wrote:
>
> > Hm.
> >
> > After applying your patches, my build halts with:
> >
> > BUILD FAILED
> >
> > Target `docs' does not exist in this project
> >
> > even when just doing ./build.sh clean
Sorry, the patch is imcomplete. :-/ My fault.
This one should work.
You also need to do this after applying:
1. move jars from ./tools/cocoon/lib to ./lib/core, and remove placeholder
file there
2. remove ./tools/cocoon dir entirely
3. remove from /tools/centipede/targets/docs.xtarget
I retained the 'docs' target instead of xdocs. I want to use forrest for it
starting from next Centipede release.
--
Nicola Ken Barozzi barozzi@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
RE: [PATCH] New fdoc build target (was Re: migrating to the new DTD's)
Posted by Steven Noels <st...@outerthought.org>.
grmbl - ctrl-enter again :-(
Steven Noels wrote:
>
> Hm.
>
> After applying your patches, my build halts with:
>
> BUILD FAILED
>
> Target `docs' does not exist in this project
>
> even when just doing ./build.sh clean
>
> I played around a bit, moving the original docs.xtarget form centipede
> to /src/targets, which then fails with /tools/cocoon/conf not found
> coming from docs.xtarget:
>
> <!-- Copy Cocoon configuration (cocoon.xconf) -->
> <copy todir="${build.context}" filtering="off">
> <fileset dir="${tools.dir}/cocoon/conf"/>
> </copy>
>
> Furthermore, I still see references to the old cocoon dir in
> tools/centipede/targets/init.xtarget:
<property name="cocoon.dir" value="${tools.dir}/cocoon"/>
<property name="cocoon.lib.dir" value="${cocoon.dir}/lib"/>
Since I'm not too familiar with the intricacies of applying patches, it
could be possible that I did something wrong, but it seems to me that
your patch is incomplete.
Nicola?
</Steven>
RE: [PATCH] New fdoc build target (was Re: migrating to the new DTD's)
Posted by Steven Noels <st...@outerthought.org>.
Hm.
After applying your patches, my build halts with:
BUILD FAILED
Target `docs' does not exist in this project
even when just doing ./build.sh clean
I played around a bit, moving the original docs.xtarget form centipede
to /src/targets, which then fails with \tools\cocoon\conf not found
coming from docs.xtarget:
<!-- Copy Cocoon configuration (cocoon.xconf) -->
<copy todir="${build.context}" filtering="off">
<fileset dir="${tools.dir}/cocoon/conf"/>
</copy>
Furthermore, I still see references to the old cocoon dir in
init.xtarget:
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:barozzi@nicolaken.com]
> Sent: vrijdag 1 maart 2002 11:31
> To: forrest-dev@xml.apache.org
> Subject: [PATCH] New fdoc build target (was Re: migrating to the new
> DTD's)
>
>
> From: "Steven Noels" <st...@outerthought.org>
>
> > Thanks for clearing this out, this really frees us from the ana/para
> > loop!
>
> ana/para? *giggle* never heard of this.
>
> > Would you be interested in doing this yourself?
>
> No prob.
> Here is the patch.
>
> After applying the patch you also need to:
> 1. move jars from ./tools/cocoon/lib to ./lib/core, and
> remove placeholder
> file there
> 2. remove ./tools/cocoon dir entirely
> 3. remove from /tools/centipede/targets/docs.xtarget
>
> I retained the 'docs' target instead of xdocs. I want to use
> forrest for it
> starting from next Centipede release.
>
> --
> Nicola Ken Barozzi barozzi@nicolaken.com
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
[PATCH] New fdoc build target (was Re: migrating to the new DTD's)
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
From: "Steven Noels" <st...@outerthought.org>
> Thanks for clearing this out, this really frees us from the ana/para
> loop!
ana/para? *giggle* never heard of this.
> Would you be interested in doing this yourself?
No prob.
Here is the patch.
After applying the patch you also need to:
1. move jars from ./tools/cocoon/lib to ./lib/core, and remove placeholder
file there
2. remove ./tools/cocoon dir entirely
3. remove from /tools/centipede/targets/docs.xtarget
I retained the 'docs' target instead of xdocs. I want to use forrest for it
starting from next Centipede release.
--
Nicola Ken Barozzi barozzi@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
RE: migrating to the new DTD's
Posted by Steven Noels <st...@outerthought.org>.
Nicola wrote:
> Now a solution going round-trip in my head neurons finally
> arrived to "me"
> ;-)
> This is what we can do: remove the cocoon tool from the
> ./tools dir, move
> those libs in ./lib/core, make an fdocs target in
> project.xtarget and use
> that.
> In this way we don't use the cocoon centipede tool for the
> docs but forrest
> itself.
> Yes, I definately like this, since it removes dependency from
> Centipede
> totally, and it makes it easy for me to make a forrest tool
> from it for
> Centipede.
+100
Thanks for clearing this out, this really frees us from the ana/para
loop!
Would you be interested in doing this yourself? I'm pretty sure my Ant
skills are no fair match to yours :-)
</Steven>
Re: migrating to the new DTD's
Posted by Nicola Ken Barozzi <ba...@nicolaken.com>.
From: "Steven Noels" <st...@outerthought.org>
> Hi,
>
> I've been trying to get Forrest to use the new v1.1 version of the DTD's
> yesterday, and found some strange behaviour in the entity resolver: if
> you put a comment (--) at the end of the catalog file, Cocoon gets in an
> endless loop of sorts.
freaky
> [...] should we fully isolate Forrest & Centipede from each
> other?
>
> With regards to my regular question on the unit of deployment that
> Centipede should produce for Forrest: will we be re-using the cocoon
> libs from Centipede for Forrest? Or will we put up a separate cocoon
> config (xconf/xmap/etc) for the forrest.war...?
Now a solution going round-trip in my head neurons finally arrived to "me"
;-)
This is what we can do: remove the cocoon tool from the ./tools dir, move
those libs in ./lib/core, make an fdocs target in project.xtarget and use
that.
In this way we don't use the cocoon centipede tool for the docs but forrest
itself.
Yes, I definately like this, since it removes dependency from Centipede
totally, and it makes it easy for me to make a forrest tool from it for
Centipede.
:-)
--
Nicola Ken Barozzi barozzi@nicolaken.com
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------