Initial directory structure.
initial import of the Eclipse project

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Perspectives: avoid Javadoc warning

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Moved files around to follow the Maven model

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
POM: use Eclipse compiler so the tests compile

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
POM: use CDATA block for the description

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Updated Eclipse launch configurations with new paths and project name

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Removed Eclipse project from version control

"mvn eclipse:eclipse" can generate it just fine, and it will need to be
run anyway, since that's how the dependencies (Objenesis and JUnit)
will be fetched.

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Replaced Ant buildfile with custom maven-assembly-plugin assembly descriptor

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
POM: add SCM information

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
POM: add Sonatype parent and a link to the Google Code issue listing

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
FastClonerHashSet: use LinkedHashSet to fix bug with changing hash entry order during cloning

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
Update POM version

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
POM: removed useless <distributionManagement> section

From: Antonio García Domínguez <antonio.garciadominguez@uca.es>
[maven-release-plugin] prepare release 1.7.4
[maven-release-plugin] prepare for next development iteration
Should have used /trunk in the <scm> element
POM: retrying bad release 1.7.4
[maven-release-plugin] prepare release 1.7.4
[maven-release-plugin] prepare for next development iteration