* lacolla-1.0.7.jar 
 - Now the user can specify the environment variable LACOLLA_HOME, so s/he can start LaCOLLA in a directory other than its home. If not set, LACOLLA_HOME will be set to the current directory.


* lacolla-1.0.6.jar 
 - It fixes the bug that disseminates always the events with eventType 'read' .

* lacolla-1.0.5.jar 
 - It fixes a bug with the logging messages when doing a getObject operation that was a source of confusion - The message "Objecte rebut"â were being printed even if when the object could be found by LaCOLLA.

* lacolla-1.0.4.jar
 - UA keeps control of duplicated events
 - A new login API has been added with the TimestampSummary of the
     application to send the summary of events.
 - no java.policy is needed
 - no RMISecurityManager is needed


* lacolla-1.0.3.jar
 - Fixes getInfoMember operation
 - Fixes addGroup operation


* lacolla-1.0.2.jar
 - Fixes the BufferLaCOLLA.remove exception
 - Uses the log4j package to create logs. The default configuration file is located in
   /resources/config/log4j.xml (inside de jar file). By default, the configuration will
   print all the messages to console.  Alternatively you can customize your own
   resources/config/log4j.xml file and make your CLASSPATH point to the location of 
   the resources directory BEFORE the path to the lacolla library.
 - It can use ANT to start LaCOLLA. Targets:
	ant clean
	ant lacolla
 - IMPORTANT: Includes the changes of lacolla-1.0.1.jar. 
   Please follow the comments of lacolla-1.0beta



* lacolla-1.0.1.jar
 - Fixes the RA-directory access exception
 - IMPORTANT: Includes the changes of lacolla-1.0.1.jar . 
   Please follow the comments of lacolla-1.0beta


* lacolla-1.0beta
 - Adds an RMISecurityManager to read the java.rmi.server.codebase from the applications.
 - You must start LaCOLLA with the -Djava.security.policy=java.policy property set.
 - Create a java.policy file in your LACOLLA_HOME like this:
   grant {
 	permission java.security.AllPermission;
   };