Developer guidelines modified by Luca Longinotti

Luca Longinotti — Mon, 24 Jun 2013 16:54:19 -0000

Please follow these guidelines on committing jAER code.

put all your work in your own packages named appropriately; use whatever is your DNS domain name for your organization, you can see some examples like ch.unizh.ini.jaer.chip.dvs320 in the project.
don't commit jAER.jar as a general rule
make sure whatever you commit builds clean and that have added/committed all classes - you might be able to build but others wont because they don't have all the classes. this is easy if you simply commit all the .java files you're using in your package source folder
don't commit binarys or just everything you have, just source code.

don't use system.println . Instead, make a Logger and use it to log outputs. For example,

// in the class header
private static Logger log = Logger.getLogger("net.sf.jaer");

// somewhere in one of your methods
log.info("this is a log message");
log.warning("something bad happened");

Recent changes to Developer guidelines

Developer guidelines modified by Luca Longinotti