cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Compilation problems was RE: [Fwd: freshmeat project listing for Cocoon]
Date Fri, 23 Nov 2001 11:28:36 GMT


> -----Original Message-----
> From: giacomo [mailto:giacomo@apache.org]
> Sent: Friday, November 23, 2001 12:01 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: Compilation problems was RE: [Fwd: freshmeat project
> listing for Cocoon]
>
>
> On Fri, 23 Nov 2001, Carsten Ziegeler wrote:
>
> > > Giacomo Pati wrote:
> > >
> > > On Thu, 22 Nov 2001, Carsten Ziegeler wrote:
> > >
> > > > Just to get it right. The following is the text we agree on.
> > > > I'll try my best to get it into freshmeat then....
> > > > By the way, shouldn't we change the README or some other documents
> > > > and add this text there?
> > >
> > > Yes, freshmeet (including the version number there, it's still 1.8.3
> > > IIRC), and README. I've commited the xdocs/indeex.xml page
> containig the
> > > text. Unfortunately I wasn't able to compile the repository because
> > > something has changed concerning the PhpGenerator (and I was
> toooo lazy
> > > to find out why).
> > >
> > I changed yesterday the checking of the optional compilation. The old
> > algorithm
> > did copy e.g. the PhpGenerator to the build.src directory but
> didn't compile
> > it.
> > Other optional components were not copied beforehand. So there were two
> > places
> > checking: when copying sources and when compiling.
> > I unified this. The checkings is now only done during copying.
> So, if you do
> > a build clean first, it should work then - if not, let me know.
>
> Big no. After a clean checkout of the HEAD I was able to compile
> but building the docs failed havily.
>
> Could someone fix that more familiar with it than I am? I think it has
> to do with the DTD resolver whcih cannot find the DTDs requested during
> the build of the docs (even if I've sound them to be there where it
> complains wouldn't be there).
a "build docs" works perfectly here. Hm

Carsten

>
> Giacomo
>
> >
> > Carstn
> >
> > > Giacomo
> > >
> > > >
> > > >
> > > > ------------------------------ OO ---------------------------------
> > > >
> > > > Apache Cocoon is an XML publishing framework that raises
> the usage of
> > > > XML & XSLT technologies for server applications to a new
> > > > level. Designed for performance and scalability around pipelined SAX
> > > > processing, Cocoon offers a flexible environment based on
> the separation
> > > > of concerns between content, logic and style. A centralized
> > > > configuration system and sophisticated caching top this all
> off and help
> > > > you to create, deploy & maintain rock-solid XML server applications.
> > > >
> > > > Cocoon interacts with most data sources from filesystems to
> RDBMS, from
> > > > LDAP to native XML databases and adapts content delivery to the
> > > > capabilities of different devices like HTML, WML, PDF, SVG,
> RTF just to
> > > > name a few. Cocoon currently runs as a Servlet or from a powerful
> > > > commandline interface. The choosen design of an abstracted
> environment
> > > > gives you the freedom to implement your own concrete
> environment to let
> > > > it work.
> > > >
> > > > ------------------------------ OO ---------------------------------
> > > >
> > > >
> > > > Carsten
> > > >
> > > > > -----Original Message-----
> > > > > From: Gianugo Rabellino [mailto:gianugo@rabellino.it]
> > > > > Sent: Thursday, November 22, 2001 12:07 PM
> > > > > To: cocoon-dev@xml.apache.org
> > > > > Subject: Re: [Fwd: freshmeat project listing for Cocoon]
> > > > >
> > > > >
> > > > > giacomo wrote:
> > > > >
> > > > > > On Wed, 21 Nov 2001, Gianugo Rabellino wrote:
> > > > > >
> > > > > >
> > > > > >>giacomo wrote:
> > > > > >>
> > > > > >>
> > > > > >>>Ok, here is what I feel hits the point :)
> > > > > >>>
> > > > > >>>----------------------------------- oo
> > > > > -----------------------------------
> > > > > >>>
> > > > > >>>Apache Cocoon is an XML publishing framework that raises
> > > the usage of
> > > > > >>>XML & XSLT technologies for content-centric server
> > > > > applications to a new
> > > > > >>>level. Designed for performance and scalability around
> > > pipelined SAX
> > > > > >>>processing, Cocoon offers a flexible environment based
on the
> > > > > separation
> > > > > >>>of concerns between content, logic and style. A centralized
> > > > > >>>configuration system and sophisticated caching top this
all
> > > > > off and help
> > > > > >>>you to create, deploy & maintain rock-solid XML server
> > > applications.
> > > > > >>>
> > > > > >>>Cocoon interacts with most data sources from filesystems
> > > to RDBMS, from
> > > > > >>>LDAP to native XML databases and adapts content delivery
to the
> > > > > >>>capabilities of different devices like HTML, WML, PDF,
> > > SVG, RTF just to
> > > > > >>>name a few. Cocoon currently runs as a Servlet or from
> a powerful
> > > > > >>>commandline interface. The choosen design of an abstracted
> > > environment
> > > > > >>>gives you the freedom to implement your own concrete
> > > environment to let
> > > > > >>>it work.
> > > > > >>>
> > > > > >>>----------------------------------- oo
> > > > > -----------------------------------
> > > > > >>>
> > > > > >>
> > > > > >>
> > > > > >>Sounds good to me. Just another small note:  I'm not *that*
> > > sure about
> > > > > >>focusing on the "content-centric" concept. I do believe
> > > that Cocoon is
> > > > > >>not just for content but can be seen as a generic and very
> > > powerful XML
> > > > > >>processing environment. We have XSP, we have SOAP, we have
> > > actions and
> > > > > >>we will have flowmaps: are we sure that we want to "sell"
> > > Cocoon once
> > > > > >>again mainly as a presentation engine for content-oriented
> > > sites? I'm
> > > > > >>afraid that people looking at the freshmeat blurb might
> > > look at it and
> > > > > >>just say "oh, ok, this is yet another XSLT tool"...
> > > > > >>
> > > > > >>Just another 0.2 euros, other than that I really like
> the result :)
> > > > > >>
> > > > > >
> > > > > > Would you simple remove that word from the abstract above?
> > > > >
> > > > >
> > > > > Exactly, good suggestion. "server applications" is way enough.
> > > > >
> > > > > Ciao,
> > > > >
> > > > > --
> > > > > Gianugo Rabellino
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > > > >
> > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message