FAQs

1. Why can't I see the class EntityManagerFactory ? It does not exist!

   Please clean, recompile and refresh your source code. If you encounter a compilation error, activate debug to access the root cause. It can be done in command line with mvn clean compile -X. The -X option activate verbose log messages. You may want to redirect the output to a temporary file for analysis later: mvn clean compile -X > /tmp/logs.txt

2. I often have compilation error after updating my entities

   You need to clean, recompile and refresh your source code so that the changes you made triggers new source code generation

3. Any support for property indexing & text search ?

   Technically possible by putting Lucence in the loop but lots of work to do. You're welcomed to help.

   For those who have some money, Datastax offers a custom version of Apache Solr with Cassandra under the hood, which boost the performance. Check it out, it's quite nice

4. If I spot a bug in Achilles, how can I have it fixed ?

   First, you can report the bug on the mailing list and in GitHub by creating an issue

   Generally, detected bugs are fixed quite fast. If you want it to go faster, just fix it yourself and propose a pull-request.

5. How can I have new features in Achilles ?

   Same answer as for point 2. Create a new issue or preferably a pull-request. I will be happy to merge it into the master branch

6. How can I contribute to Achilles ?

   The most important contribution you can do for Achilles is using it extensively and report bugs. Right now the framework is quite mature and most of obvious bug have been spotted & fixed. However there are still corner cases we might have missed.

   If you want to propose a pull-request, please respect the following points:

   1. Each new feature/piece of code added to the code base should be at least unit-tested
   2. Add a new integration test (IT) whenever possible for the new code