cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ken Barozzi" <baro...@nicolaken.com>
Subject Re: [PATCH] new build targets
Date Wed, 23 Jan 2002 08:27:55 GMT

----- Original Message -----
From: "David Crossley" <crossley@indexgeo.com.au>
To: <cocoon-dev@xml.apache.org>
Sent: Wednesday, January 23, 2002 8:25 AM
Subject: Re: [PATCH] new build targets


> Hi Nicola Ken, today i added your patches for the new
> "interactive" and "patchqueue*" targets. Many thanks,
> these work well.

:-) Thank you.

> I tried the "patchqueue-xdocs" target and that worked nicely
> to get the listing directly from Bugzilla and create an xdoc.
> Very good. However, i have not yet tried "build docs" to be
> sure that all is OK with the generated xdoc (would you please).

It worked before submitting. I re-tried it from CVS it and the docs build
(without the dynamically generated xdoc) fails for me during sitemap
compilation:

     [java] Sitemap location = sitemap.xmap
     [java] Checking sitemap reload = true
     [java] Reloading sitemap asynchron = true
     [java] Sitemap check delay = 1 sec
     [java] INFO    10117   [        ] (): Warming up...
     [java] INFO    10117   [        ] ():  [Cocoon might need to compile
the sitemaps, this might take a while]
     [java] ERROR   10117   [        ] (): Logicsheet.getTransformerHandler:
Exception
     [java] org.apache.cocoon.ProcessingException: Error in creating
Transform Handler: org.xml.sax.SAXParseException: General Schema Error:
Grammar with uri: http://www.w3.org/1999/XSL/Transform , can not be found;
schema namespace may be wrong:  Xerces supports schemas from the
"http://www.w3.org/2001/XMLSchema" name
space or the instance document's namespace may not match the targetNamespace
of the schema.
     [java]     at
org.apache.cocoon.components.xslt.XSLTProcessorImpl.getTransf
ormerHandler(XSLTProcessorImpl.java:223)
     [java]     at
org.apache.cocoon.components.language.markup.Logicsheet.getTr
ansformerHandler(Logicsheet.java:144)
     [java]     at
org.apache.cocoon.components.language.markup.Logicsheet.getNa
mespaces(Logicsheet.java:126)


> I did not try the "patchqueue" targets that send notifications
> to the mail lists.

Just did it. See if it shows up on the list.

> By the way, i presume that an ordinary user
> will be able to use those targets. Is that what we want?

Good point. We don't want ordinary users to use it, but how can we prevent
it?

> The interactive build worked fine for me
> ./build.sh -buildfile build-i.xml
>
> I found only a few issues ...
>
> 1) The directory tools/src is getting to be a bit haphazard now.
> Does it need some structure?

Also the module root yis a bit crowded IMHO.

> 2) ASCII art ... i do not see the need for this. To me it is just
> clutter. However i committed it anyway. What do others think?

The intention of it is to make users percieve that Cocoon is not a hack. For
some it could have the opposite effect, though. :-!  Whar is the idea others
get from it :-?

> 3) You will need to add some xdoc documentation somewhere
> about how to use these new facilities. Your email below is
> a good start for the words.

+1

> 4) When this new functionality is properly settled we need to
> add an entry to changes.xml

Never do by hand what the compy can do 4 you ;-) How about a new target that
changes the changes.xml document based on the changelog?
I'm working on it.

--
Nicola Ken Barozzi                 xml-cocoon@nicolaken.com
These are the days of miracle and wonder...
          ...so don't cry baby, don't cry...
                                                  Paul Simon




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


Mime
View raw message