Hi All,
I note the topics to be discussed around doc and packaging:
- Default conf, maybe more than one depending on user profile (small
server,...) and techno (file mailserver, database mailserver,...)
- Custom conf : how can users easily change the confs
- Migration: the MIGRATE.txt should simply contain the URL of the page
where the migration is described. This page will be the usermanual of
coming migration tool (JAMES-1052 and JAMES-1090)
We certainly cover these reviewing the web site.
The issue with jmx.password on windows is new (3 days old since jmx
security is activated).
Sure, it will be documented on website, but I wonder if this will not
represent a *real blocking factor for james.* User will directly say:
"it does not work!" and will not try to solve issue, even if it's
documented.
Tks,
Eric
On 27/10/2010 07:25, Norman Maurer wrote:
Hi Stefano,
comments inside..
2010/10/27 Stefano Bagnara<[email protected]>:
2010/10/26 Norman Maurer<[email protected]>:
I'm very happy to start a VOTE for the first milestone of the
upcomming major version of JAMES Server (3.0). This milestone include
tones of improvements,features and bugfixes.
That's great! :-)
I think one of the most important things for "normal" users is the
support of IMAP and the new fastfail stuff in SMTP. To get a complete
list see:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10411&styleName=Html&version=12314294
Here are the artifacts for review:
https://repository.apache.org/content/repositories/orgapachejames-001/
So please cast your VOTE:
[X] +1 Yes please release
Few points/questions/hints for M2:
1) running it under windows says:
"Errore: Limitare l'accesso in lettura al file password: ../conf/jmx.password"
(Trans: error: you have to limit read access to password file:
../conf/jmx.password). It's not clear what I have to do to limit this
access and whom to limit access to.
Welcome to windows ;) When running JAMES on a unix-like platform you
don't see this error as the configuration files come with perms 0600.
Anyway its documented in the JMX docs.
See:
http://download.oracle.com/javase/1.5.0/docs/guide/management/security-windows.html
I already talked with Eric and he will add it to the website.
2) in a future version I'd like to see some dependency removed from
the binary release (e.g: pdfbox-1.0.0.jar is 4.6MB and I believe it's
not really used but only transitively inherited by jackrabbit).
Makes sense, pdfbox is only needed to index pdf files in jackrabbit.
So no need to ship it with JAMES. I will open a jira for it.
3) we now have a lot of implementations for each api. Even to me (long
time james user/developer) it's now not obvious what are the default
or the preferred implementations and their status. Maybe we should
provide a small table indicating defaults and pro/cons of the various
implementations when it's not obvious.
It's not clear what is the best setup for users that only needs a
small mail server with no database, or what is suggested to users that
wants to set up a cluster with no "file" state in the nodes, and
similar "standard" things.
+1 Something for the website. Eric ? ;)
4) in the source distribution we have the STATUS file: IMHO this
should be removed from there and from SVN. It was a failed experiment.
+1 will do.
5) MIGRATE.txt is outdated. It's better to remove it that to have it
documenting a bad migration path.
+1 We will have to write one when the api is stable.
6) In James 2.3 we had a README.txt with some docs, and with the
Crypto Notice. I guess at least Crypto Notice should be revamped.
Will have a look for M2 or whatever the next release will get called.
Stefano
Bye,
Norman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
