Implement onHandleIntent for @EIntentService according to issue #572
Add @ServiceAction methods in IntentBuilder
Add functional tests
Allow injection of bean and other AA annotations in @EIntentService
Fix a bug with primitives and stop execution as soon as an action match
Refactoring common code between ServiceActionProcessor and ExtraProcessor

Refactoring three parts : addCastMethod, addIntentBuilderPutExtraMethod and camelCaseToUpperSnakeCase
Fix javadocs and rename some variables
Add functional tests
Check if there is duplicate method names
Add some information about the context of the crash
Add java compiler version in crash report
Add AA version
Add information about enclosing element in crash report
Fix a NullPointerException throwing during refactoring. Let the compiler inform the developer about the missing constant
Use ElementUtils from ProcessingEnvironment to print the context instead of home-made system
Uses a property instead of a constant for AA processor version
Write AA version used in generated header files
Fix IntentBuilder startForResult

In a fragment, startActivityForResult must be called on the Fragment and
not on getActivity(), or the fragment's onActivityResult will never be
hit.

Now IntentBuilder may have up to 3 constructors, depending on the
classpath content. According to the constructor chosen,
startActivityForResult will be called on Activity, android.app.Fragment
or android.support.v4.app.Fragment.

From the AA user perspective, this fix is quite transparent, he just
have to call MyActivity_.intent(this), whatever he's in a Fragment or an
Activity, it will work.
Support for injection of android.content.ClipboardManager by @SystemService
Use new method to check class in classpath