Coding and projects standards for phpeclipse

Hi:
I did some overall cleanup and formatting on the code.
I would like to agree on some common standards going forward.
Here is what I suggest:
- we use only Java 1.4 (and NOT 1.5) , so we stay Linux freindly, and
are usable on more platforms.
- we use the standard Eclipse coding style and formats.
- we use Eclipse 3.2.x for development
- I tend to prefer the systematic use of braces for blocks like if/then,
try/catch and so on. Would that work out for everyone?
- we do not commit fixes to bugs and or new features without committing
a JUnit test for it. 
For that we will use one test fragment for each plugin project.  See the
net.sourceforge.phpeclipse.test for a sample of such a fragment 
- always use a commit message in a commit, and prefix the commit
messages with: Bug xxxxxx when a commit is for a specific tracker at
Sf.net
What do you think?


-- 
Cheers
Philippe

philippe ombredanne | 1 650 799 0949 | pombredanne at nexb.com 
nexB - Open by Design (tm) - http://www.nexb.com 
http://easyeclipse.org  -  irc://irc.freenode.net/easyeclipse




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642