Stefano,

> Sorry but I have not found the right thread looking in the mailing list

Heck, I am impressed that you *tried*!  :-)  Some of this stuff is buried
ages ago.  Along with discussions about Maven vs Ant and Forrest vs Maven vs
Anakia.

Yes, the docs were not merged intentionally.  I seem to recall a comment or
two back in that merged thread about the docs, but it would have been in the
context of earlier discussions.

Had you never noticed that we even have a site-dev@ mailing list?  The site
was supposed to become a separate "project."

> > We deliberately setup the site project, and should should move the web
site
> > xdocs to there.  We are supposed to split the site docs from the version
> > specific project docs, so that each release would have its own place on
the
> > site.

> What are the advantages of keeping the xdocs on a different project?

When you have multiple releases, you run into a problem maintaining the
separate portions of the site for each release, such as release-specific
javadoc and other docs; as well as the overall site, itself.

> I would prefer to split it in a separate module if we move to maven2
> multiproject setup

I am looking into how to do multi-project in Ant.  It appears that the
<subant> task (http://ant.apache.org/manual/CoreTasks/subant.html) can solve
the problem for us.

> I simply didn't understand anything seeing changes in html and
> not it the xdocs file that generated them. Have you a local
> xdocs or you started changing directly the html?

Normally, we generate the .html from the xdocs, and store both in SVN.  The
web site is updated directly from SVN.  On a very few occasions, I may have
made a minor change directly to .html, but that would not be normal.

> I thought we first should fix it in trunk, when we reach a good
> setup we backport to 2.3.

Yes, we've been down that road before.  Isn't pretty.  Which is why we split
the site into its own project.

> if you already voted about some sort of roadmap for the xdocs can
> you point me to the correct thread/wiki/other information so I
> can try to fix this issue?

It must have been years ago.  Danny or Serge proposed it.  I think it was
Danny at one point when he had more time.  But Serge and I definitely saw
the problem when we were trying to maintain copies in the v2 branch and
trunk.  It was a mess.  Not fun.  So when I did the merge, it was
intentional that the xdocs were not brought over.  But now we need to
complete the job, and get the site project going.

And I think it is time to upgrade our Ant to 1.6.5; or perhaps remove Ant
from our repository, and ask developers to install it first.

        --- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to