* Started to refactor.

* The contents of the 'dml' module were copied to new-fenix-framework-core.

* Renamed packages

* Removed specific references to FF-for-JVSTM-OJB

* jvstm-ojb-code-generator contains some files that will probably be removed.
  Others are here because they are specific to FF with jvstm/ojb
* Again renamed packages.  Here's the breakdown on the names (prefix is
  pt.ist.fenixframework):

  * <top-level>: public API classes used to develop applications with the
    Fenix Framework such as FenixFramework, Config, DmlCompiler, DomainObject,
    TxManager, etc.

  * dml: DML classes, DomainModel, Slot, Relation, etc.

  * dml.runtime: Classes used in the dynamically generated domain classes
    (RoleOne, RoleMany, etc.)

  * dml.antTasks: ANT task to call the DmlCompiler

  * core: implementation of the core framework.  These will be most of the
    classes previously in pstm and its sub-packages.

* Renamed jvstm-ojb-code-generator to code-leftover-from-refactoring

* A few more things moved out of new-fenix-framework-core to
  code-leftover-from-refactoring.
* Current version already allows a very simple application to work

* Removed unnecessary pom dependencies

  new file:   src/main/java/pt/ist/fenixframework/Config.java
  new file:   src/main/java/pt/ist/fenixframework/FenixFramework.java
  new file:   src/main/java/pt/ist/fenixframework/FenixFrameworkPlugin.java
  new file:   src/main/java/pt/ist/fenixframework/TransactionalCommand.java
  modified:   src/main/java/pt/ist/fenixframework/dml/PojoCodeGenerator.java
  new file:   src/main/java/pt/ist/fenixframework/dml/runtime/RelationAwareSet.java
* Changed external representation type of DomainObject from Object to
  Serializable.
* No longer support for FenixFrameworkPlugins (maybe later, but for now
  appears not to be needed).

* Config now takes a URL[] to the location of DML files. closes #1.
* New: Create a ConfigurationManager. closes #6

* Added (yet incomplete) interfaces for TransactionManager and Repository
* Removed method DomainObject.fromExternalId(Serializable oid).  The way to get a domain object is via FenixFramework.getDomainObject(Serializable externalId).

* ConfigurationManager renamed to ConfigurationExtension. Related to issue #6.

* FenixFramework class is the main class in the framework.  It is a Facade for accessing the TransactionManager and getting a DomainObject from the underlying ConfigurationExtension.
DmlCompiler to support local and external DML specs

Closes #11.
Support only one DomainModel

 * Closes #5
DomainObject.getExternalId() should return String instead of Serializable

 * closes #14
Implement a default AbstractDomainObject in core

* Closes #9.

* Fixed getDomainClassRoot() in pt.ist.fenixframework.dml.PojoCodeGenerator to
  return the String refering the CoreDomainObject.
* Fixed potential NullPointerException when config was null in
  FenixFramework.initialize().

* Eliminate the ConfigurationExtension. It was unnecessary, given that
  subclassing Config is enough.

* Split Config in two: Config and DefaultConfig.  The latter is for the
  fenix-framework-core.

* Added ConfigError class to make configuration errors programmatically more
  explicit.
Update the initialization mechanism

 * No longer uses a 2-step initialization. Closes #2.

 * Support explicit initialization (the programmer created the Config class
   and calls FenixFramework.initialize()), and initialization by convention
   (the programmer provides a fenix-framework.properties file in the
   classpath).  See more documentation on the javadoc for FenixFramework and
   Config.
Merge remote-tracking branch 'origin/develop' into smf-big-refactoring-2012
Several refactorings on dml-maven-plugin and DmlCompiler

* Update dml-maven-plugin to use new-fenix-framework-core (partially finished)

* Update DmlCompiler for a cleaner API using CompilerArgs.  Also, just getting
  the DomainModel is more streamlined.

* Added some (domain-specific) exceptions to give more context to the things
  thrown.

* Update DmlCompileTask and DmlCodeGeneratorMojo to take into account the
  changes in the API of the DmlCompiler.

* Start work on DmlPostProcessorMojo.  Removed dependency from
  jvstm.ProcessAtomicAnnotations, but still not finished.
Merge remote-tracking branch 'origin/develop' into smf-big-refactoring-2012
Refactor dml-maven-plugin

 * Closes #17. Closes #18.  However, the PostProcessor is only injecting the
   required constructor.  It is not yet processing the @Atomic annotation.
   But, at least, it compiles without errors.
Enhancement: There are now a set of archetypes to create fenix-framework projects configured with the default back-end
Modify the fenix-framework-archetype to comply with the new architecture
This closes #20. Now fenix-framework considers a new project aggregator called fenix-framework-archetypes, where the three different
archetypes are defined: module, application and web-application.
Upgrade from asm3 to asm4

* Closes #25.