Henri Yandell wrote:
A lot of projects at Jakarta seem to use Maven now.I'm not so bothered by who uses Maven, but by who is using Maven for their websites. The L&F and structure is different to the primary top level Jakarta site. My only question here is: Should I push this on general@jakarta, or initially at maven@jakarta?
I would suspect you want 'general'. Or even 'infrastructure'.
Yes, it would be nice if Jakarta had a consistent information architecture. Yes, maven can help with that (look at the 'Project Documentation' section on mavenized sites). Yes, Jakarta should have a consistent look. Yes, maven can help with that (you can reskin it if you want).Does anyone here agree with me? and are there any features of the Maven site generation which would help?
However, Jakarta is a loose federation of projects; not everyone is going to want to use maven. Much as it might be anathema to say it on this list[1], the project which is trying to do what you ask is Forrest. Their explicit goal is to aggregate xml documentation from many projects and create a consistent site out of that. There was some chat a month ago on the subject of creating a forrest plugin for maven (http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]&msgId=576278).
This doesn't help with everything - Forrest does not currently have anything you could call an 'information architecture'[2], it lets you put anything pretty much anywhere. Maven is much better at this, it provides a 'project documentation' section which /is/ consistent across projects, because its entirely generated for you. The only 'standard' link maven is missing is a 'download' link for releases, but it wouldn't be difficult to standardize this and more of the jakarta navigation stuff.
-Baz
[1] Forrest involves Centipede. 'nuff said.
[2] Its on their 'dream list'. Compare, eg. http://ant.apache.org with http://xml.apache.org/forrest. Even the names of the links to the bug tracker are different.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
