Build Broken in HEAD revision
-----------------------------
Key: JAMES-333
URL: http://nagoya.apache.org/jira/browse/JAMES-333
Project: James
Type: Improvement
Environment: Windows/FreeBSD, JDK 1.4.2
Reporter: Brill Pappin
The developers of James have done a wonderful job with the concept of James up
to this point although have been a little slow in the development process.
However, I could not wait for the fixes to come in and so decided to tackle a
few of the more critical problems myself... in trying to fix the large number
of bugs in James I've found, and trying to test the IMAP implementation, I
checked out the HEAD revision and attempted to build. Once I'd solved the
dependency mess, I found that the code was actually broken in relation to the
com.apache.james.util.connection.* classes and their super classes.
I also found very little or no unit tests, so I could not determine what part
of the code exactly was broken (or what it should do).
The code base is pretty much a mess as far as I can tell but I can suggest a
few things that would help keep this project on track: Use Agile, TDD processes
in your development. Use Maven for a build system.
I am willing to port the project to a Maven build if requested to do so.
I would also like to see some unit test for this code.
Yes, this ticket is pretty harsh, but as experienced developers, I expect
better.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
