Yo guys,
I've recently restructured the MAPI CVS structure. The
original src/ directory is still available, but as of now
kind of outdated and obsolete. If anyone wants to make
changes to it, be sure to checkout & commit the mapi/
directory instead of src/.
I'm browsing through the source as of now, mostly adding
major javadoc comments right here and there. I'm leaving
stuff out of the docs since I just got no idea what some
things are doing. I am also refactoring some stuff
(changing package names, methods) and just checking how the
whole is put into place.
I am trying to realize Stig's idea to seperate the core
classes from the Mailsomething application. If we want to
achieve this, no one should be modifying, adding, or
removing biiiig stuff in the mailsomething project. If we
do this the whole bunch will get inconsistent and we will
have different versions which we need to integrate into the
MAPI project, which will result in endless pain, hell and
brain explosions (.. you get the idea :P)
I just don't know how we can realize this in the best way.
There is one option which is the following:
Generating a JAR from the MAPI project, and include that
one in your classpath of the mailsomething project. I just
don't know the version differences. If there are major
versions difference, I urge Stig (plz :D) to extract the
core classes into the MAPI project.
---
Other stuff:
If your IDE supports task tags, please add and use the
following (case-sensitive):
TODO, FIXME, XXX, BUG
If you are coding, please add Javadocs to mainly every
method and field which is either default, public or
protected. Private fields are nice too if you want to
comment them.
Kevin
|
