You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Hes Siemelink <he...@izecom.com> on 2005/01/08 00:48:38 UTC
Mailet documentation has already been updated, but is not published
on web site
Serge Knystautas wrote:
>
> Steve, can you double check this? I thought we were (screwily)
> generating the website from MAIN rather than the branch_2_1_fcs. I
> know Danny was working on sorting this out, so he might know better.
> You should be able to see how the site is checked out on minotaur for
> http://james.apache.org
>
That is correct, and somebody has been sleeping here!!
The documentation on the web site for the mailets is out of date. I have
tried to point that out in the last couple of months.
It turns out that the 2.1 branch contains an updated version of the
mailet documentation. (in the src/xdocs directory)
Please copy these files to the main branch and update the web site as
soon as possible.
Then not only people who dig into the James source can benefit from new
mailet functionality.
Thank you,
Hes.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: Mailet documentation has already been updated, but is not published on web site
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Why can't the web site be updated with the current documentation?
> Surely you don't have to wait for the Big Merge to do that?
It can be updated. Danny, I believe, is working on it. The problem is to
make sure that the UPDATED documentation is used. That will not happen by
simply copying from the branch to trunk.
What I believe that we really want to do is separate the site as a separate
component, and then add the additional component/version specific pieces.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Mailet documentation has already been updated, but is not published
on web site
Posted by Hes Siemelink <he...@izecom.com>.
Serge Knystautas wrote:
> Hes Siemelink wrote:
>
>> It turns out that the 2.1 branch contains an updated version of the
>> mailet documentation. (in the src/xdocs directory)
>>
>> Please copy these files to the main branch and update the web site as
>> soon as possible.
>>
>> Then not only people who dig into the James source can benefit from
>> new mailet functionality.
>
>
> The people who dig into the James source suffer over the branch
> problem, just like you are. There has been a merge planned for about
> a year, but we have yet to cross that line.
>
I'm sorry -- I don't follow you... I'm just getting really confused. Why
can't the web site be updated with the current documentation? Surely you
don't have to wait for the Big Merge to do that?
Hes.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Mailet documentation has already been updated, but is not published
on web site
Posted by Serge Knystautas <se...@lokitech.com>.
Hes Siemelink wrote:
> It turns out that the 2.1 branch contains an updated version of the
> mailet documentation. (in the src/xdocs directory)
>
> Please copy these files to the main branch and update the web site as
> soon as possible.
>
> Then not only people who dig into the James source can benefit from new
> mailet functionality.
The people who dig into the James source suffer over the branch problem,
just like you are. There has been a merge planned for about a year, but
we have yet to cross that line.
--
Serge Knystautas
Lokitech >> software . strategy . design >> http://www.lokitech.com
p. 301.656.5501
e. sergek@lokitech.com
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
Re: Mailet documentation has already been updated, but is not published
on web site
Posted by Hes Siemelink <he...@izecom.com>.
Noel J. Bergman wrote:
>>That is correct, and somebody has been sleeping here!!
>>
>>
>
>No. The main documentation has ONLY be updated in MAIN. And the changes in
>branch_2_1_fcs are for that version.
>
>
>
>>It turns out that the 2.1 branch contains an updated version of the
>>mailet documentation. (in the src/xdocs directory)
>>
>>
>
>Are those things that even apply to MAIN, or only to the branch? The
>problem is that we have the site building from MAIN, and product information
>in a branch. Danny is working to allow the site to be built in a separate
>site/ location, and then component specific additions can be made, such as
>the docs for a given release.
>
>
Sorry, I may have been a bit unclear. I am talking in particular about
the file src/xdocs/provided_mailets_2_1.xml
That file reflects the state of the current release (2.2) and should
therefore be published on the web site.
The file src/xdocs/provided_mailets_2_1.xml in MAIN (=web site) is outdated.
It doesn't make sense to only publish the documentation of a release
that is strongly discouraged to use on the web site, if the new
documentation is already available.
Cheers,
Hes.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org
RE: Mailet documentation has already been updated, but is not published on web site
Posted by "Noel J. Bergman" <no...@devtech.com>.
> That is correct, and somebody has been sleeping here!!
No. The main documentation has ONLY be updated in MAIN. And the changes in
branch_2_1_fcs are for that version.
> It turns out that the 2.1 branch contains an updated version of the
> mailet documentation. (in the src/xdocs directory)
Are those things that even apply to MAIN, or only to the branch? The
problem is that we have the site building from MAIN, and product information
in a branch. Danny is working to allow the site to be built in a separate
site/ location, and then component specific additions can be made, such as
the docs for a given release.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org