You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2005/12/18 03:57:09 UTC
Preparing the v2.3.0 release
I have gone back through all of the e-mail that I could find discussing the
pending release, tried to collate the notes, and edited the wiki to help
track the plans: http://wiki.apache.org/james/JamesV2.
I have time to work on the release, and plan to work on the necessary
fast-fail improvements (these are not due to the SoC changes, by the way,
but actually stem back to the fast-fail changes I had made earlier). Would
appreciate help on the build setup. And there are the JIRA issues to
cleanup, docs to write, etc. Who has time to help? :-)
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Preparing the v2.3.0 release
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> Where do we want to put the xdocs?
In site/trunk/xdocs. The plan was to separate out the tools, build.xml,
etc. for building the site, so that we would have the site as a separate
project.
So we'd have:
http://james.apache.org -- built from site project
http://james.apache.org/$product -- built from each project
where $product refers to mime4j, each currently documented version of JAMES,
etc., and contains product specific documentation and javadocs.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Preparing the v2.3.0 release
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Stefano Bagnara wrote:
>
>> Noel J. Bergman wrote:
>>> All of the site docs were moved to the site tree, outside of the code
>>> branches. The site and related build needs to be reorganized so that
>>> we have a site, plus build-specific docs in its own sub-directory.
>
>> I'm looking in http://svn.apache.org/repos/asf/james/site/trunk but I
>> cannot find xdocs there.
>
> :-( Sorry, they still need to be moved. They are in the tag that was the
> old trunk: tags/pre-v2and3-merger-trunk/src/xdocs/.
Where do we want to put the xdocs?
Should I add them back to the src/xdocs in the trunk?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Preparing the v2.3.0 release
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano Bagnara wrote:
> Noel J. Bergman wrote:
> > All of the site docs were moved to the site tree, outside of the code
> > branches. The site and related build needs to be reorganized so that
> > we have a site, plus build-specific docs in its own sub-directory.
> I'm looking in http://svn.apache.org/repos/asf/james/site/trunk but I
> cannot find xdocs there.
:-( Sorry, they still need to be moved. They are in the tag that was the
old trunk: tags/pre-v2and3-merger-trunk/src/xdocs/.
> > Personally I am very much against the use of Maven with JAMES
> I was talking about maven2 and not maven1. I agree with you about maven
> 1 and many projects reverting to ant from maven1. Your opinion is the
> same for maven2 also?
I'm used to ANT, and tend to agree with one reviewer who said "Prior to ANT
1.6, ANT had enough holes that it gave an opening for Maven to exploit. Now
that 1.6 is here, I see no reason for Maven to exist anymore. ANT isn't
anywhere near perfect, but it's reached the critical point of good enough".
See also the "Sorry to hear about Maven" thread in BSF and "Maven, help or
hinderance" thread in Jakarta Commons.
Mind you, Maven 2 seems to be held up as the "yes, maven sucks, but this
fixes it" cure, so just as Ant improved, I'll allow that Maven could
improve, too.
I'd be willing to consider maven if we avoided the use of the repository,
maven generated web-sites, etc. --- in other words, if we have a nice,
simple, clean, self-contained, build environment. But in the end, can't we
do just as well by updating our ant to the latest, and taking advantage of
ant's own multi-project support?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Preparing the v2.3.0 release
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Stefano,
>
> All of the site docs were moved to the site tree, outside of the code
> branches. The site and related build needs to be reorganized so that we
> have a site, plus build-specific docs in its own sub-directory.
I'm looking in http://svn.apache.org/repos/asf/james/site/trunk but I
cannot find xdocs there.
Could you point me to the correct folder/repository?
> Personally I am very much against the use of Maven with JAMES, and any
> number of projects that I know who use it are now looking to return to Ant.
I was talking about maven2 and not maven1. I agree with you about maven
1 and many projects reverting to ant from maven1. Your opinion is the
same for maven2 also?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
RE: Preparing the v2.3.0 release
Posted by "Noel J. Bergman" <no...@devtech.com>.
Stefano,
All of the site docs were moved to the site tree, outside of the code
branches. The site and related build needs to be reorganized so that we
have a site, plus build-specific docs in its own sub-directory.
Personally I am very much against the use of Maven with JAMES, and any
number of projects that I know who use it are now looking to return to Ant.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Preparing the v2.3.0 release
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> Would
> appreciate help on the build setup.
> And there are the JIRA issues to
> cleanup, docs to write, etc. Who has time to help? :-)
I see in the build.xml references to an xdocs folder containing xdocs
files but I can't find them in the svn repository.
Where can I find the old xdocs?
I would like to port james to maven2 but I have a few important bugs to
fix before.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: Preparing the v2.3.0 release
Posted by Stefano Bagnara <ap...@bago.org>.
Noel J. Bergman wrote:
> I have gone back through all of the e-mail that I could find discussing the
> pending release, tried to collate the notes, and edited the wiki to help
> track the plans: http://wiki.apache.org/james/JamesV2.
Great, I really appreciated this summary page!
> I have time to work on the release, and plan to work on the necessary
> fast-fail improvements (these are not due to the SoC changes, by the way,
> but actually stem back to the fast-fail changes I had made earlier). Would
> appreciate help on the build setup. And there are the JIRA issues to
> cleanup, docs to write, etc. Who has time to help? :-)
>
> --- Noel
Here are the issues I'll try to close soon:
http://issues.apache.org/jira/browse/JAMES-421
MailImpls sharing MimeMessages / LinearProcessor not cloning it after a
partial match.
http://issues.apache.org/jira/browse/JAMES-414
Add more flexibility to LocalDelivery (only partially: I think I'll
simply rename the current "ToMultiRepository" in "ToLocalRepository" or
because I never made it as flexible as I described in the issue).
And apply a couple of patches:
http://issues.apache.org/jira/browse/JAMES-423
Give the remote manager a service promt
http://issues.apache.org/jira/browse/JAMES-328
TOP <msg> 0 does not return a terminator on error
I'd like to know your opinion about upgrading phoenix to the latest
trunk. I've done it a few months ago with minor issues (I also tried Loom).
IIRC the latest trunk is more stable and used than the version we
currently bundle.
The upgrade would solve the ClassLoader issue:
http://issues.apache.org/jira/browse/JAMES-418
I think we should either upgrade now (before the 2.3beta) or never.
I'm +1 for this phoenix upgrade, if you agree I will try to run a test
and, if successfull, commit it ASAP.
I remember I would also like to deprecate a few unused
methods/interfaces so we can safely remove them in the following
release. (I need to search old notes about this)
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org