anchor.diff:  
   To activate Traces, follow this http://www.vogella.com/tutorials/EclipseCodeAccess/article.html#tracing_runonatruntime[good Lars Vogel's Tutorial]
   
  -
  +=== Test Menu
  +
  +The Test Menu has the following use-cases in mind: help qualifying an issue and aid contributing some test to Counterclockwise.
  +From menu:Clojure[Test > Generator...] you can launch what will allow you to record the UI steps needed to reproduce the problem and that most importantly will generate the necessary code for a ready-to-paste test case. This kind of contributions are very welcome as not only they provide feedback but also they consolidate the test code base.
  
positive.code: 
  - Wizards for creating / importing existing Clojure projects from scratch or from http://leiningen.org[Leiningen] project definitions
  - Clojure Editor with advanced editing features
  - Starting Clojure REPLs, interacting between Clojure Editors and Clojure REPLs 
  - Tight integration with http://leiningen.org[Leiningen] (http://leiningen.org[Leiningen] is the most popular build tool used for clojure projects)
  
  
  
negative.code: - Everytime a folder contains a `.clj` file, it is considered a 'plugin' folder.
  ** a plugin folder cannot contain nested plugin folders, only top-level scripts and non-top-level namespaces.
  - Plugin folders are processed in no specific order (plugins must be independent)
  - Processing a plugin folder consists of
  ** placing the folder inside Counterclockwise's classpath (so that you can use/require namespaces provided by the plugin)
  ** launching all the `.clj` files located at the root of the plugin, one after the other, in no particular order
  - If a plugin has several scripts, one script failing does not prevent other scripts to execute
  