On 3/11/07, TslH <[EMAIL PROTECTED]> wrote:
I'm currently looking into the maven website. If I hadn't make
mistake, there's no branches of the site for the different release.
Isn't there a way to improve the website coherency?
...
Can I suggest to apply the same kind of branches policy for maven website?
It does happen for some parts of the docs [1]. The generated docs for
the core components are published for each version. The idea of
versioning the website came up in a discussion late last year that
centered around the plugin sites [1], and the decision was to publish
the latest docs from svn, and mark new features or changes as "Since
version x.x.x".
For example, the new "mirrorOf *" syntax is documented in the Guide to
Mirror Settings [3], with a note that the section applies to Maven
2.0.5+. There was some work done in Modello so that new plugin
properties and goals would have their 'since' version automatically
generated in the docs.
And a last question: who is currently responsible for the maven website?
Everyone... and no one in particular. It's a community effort, and
for the most part, people work on what interests them. It's getting
better, particularly the plugin docs, but there is still plenty of
work to be done.
Thanks for the patch on MGN-2867. :) If you'd like to contribute
more, patches are welcome, and we also have a wiki:
http://docs.codehaus.org/display/MAVENUSER/Home
[1] http://maven.apache.org/ref/2.0.4/
[2] http://www.nabble.com/Publishing-plugin-sites-t2584348s177.html
[3] http://maven.apache.org/guides/mini/guide-mirror-settings.html
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
