Menu

Developer guidelines

Luca Longinotti

Please follow these guidelines on committing jAER code.

  1. 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.

  2. don't commit jAER.jar as a general rule

  3. 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

  4. don't commit binarys or just everything you have, just source code.

  5. 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");
    

Related

Wiki: Home
Wiki: jAER Developer Setup

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.