Re: Maven build patches accepted!

[Christopher Lenz]

Vincent Massol wrote:
Hi Julien,

-----Original Message-----
From: Julien Dubois [mailto:[EMAIL PROTECTED]
Sent: 17 September 2003 22:52
To: Cactus Developers List
Subject: Re: Maven build patches accepted!
Hi Vincent,

Some quick replies and one big question:


2 things:
- what is your strategy for xdocs? Do you plan to convert every
single
xdoc file to the maven format?
I'm just trying to keep the xdocs the way it is for the moment. For
that I
have two options
1. Trying to generate the site from Maven, as normal.
Just use my documentation/project.xml with "maven site". It's very
basic,
and
I don't know xdocs/maven enough to know if it's totally stupid or not.
But
it
might work.
No it won't. Or at least it won't give what we want. The xdocs DTDs are
different.
So now there's a DTD (or some kind of formalized schema) for the Maven 
xdocs? ;-)

I think a change to the Maven "DTTD" wouldn't be very hard, and I 
wouldn't oppose, even though I'm not very fond of the schema and would 
prefer using forrest's documentv12 (or whatever) DTD.

2. Do my own Maven goal. This would be a lot like what's Ant doing I
guess.
It's more work, and it would require some maintenance, so I'll leave
that
as
option B.
That will work and I believe this is what we should do for now. The goal
should simply do the same as is currently in the Ant build file for
generating the web site. Easy to do. 

The tricky part will be to link the Maven reports but we can leave that
for later.
- why do you need to have navigation.xml pointing to ../dtds ?
I don't need it. But in the current navigation.xml, there's a link to
that
DTD. So when Maven is working on that file, it fails to find the DTD,
and
the
build fails miserably.
I can't find navigation.xml on your web site. I'm still not sure why you
need the link to that DTD! Simply remove it. In all my navigation.xml, I
never use any reference to any DTD.
Hmm, a misunderstanding I suppose:

http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/documentation/docs/xdocs/navigation.xml?rev=1.14&content-type=text/vnd.viewcvs-markup

There *is* a "link" to the DTD, and it's relative. It's relative for the 
simple reason so that XML editors can find it. The Ant build uses a 
catalog to resolve the DTD reference, so it isn't even using the 
relative path specified.

IMHO, the current documentation story with the sitemap and the 
navigation files is a bit messy. If the Maven documentation module 
offers the functionality to generate a navigation with nested menus 
based on sub-directories *and* we can style the result so it looks like 
Jakarta/Cactus and not SourceCast/Tigris/java.net/Maven/you-name-it, 
that'd be the way to go.

-chris

--
Christopher Lenz
/=/ cmlenz at gmx.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]