arquillian/arquillian-graphene — pull request #53 by jhuska (2012-10-17 15:27:21+00:00)
Title: ARQGRA-195: refactoring of exception handling

, surefire-reporter plugin introduced, javadoc to Factory methods added

Hey Lukas,

this is just beginning of refactoring. I refactored so far exceptions which deals with proper ```@FindBy``` annotations (that is over Page Fragments and plain ```WebElement```).

In all messages I tried to provide:
* what field is wrongly annotated
* in what class is that field declared
* what can be the possible reason

I also tried somehow format error messages with new line where it is suitable. However it works only in Eclipse, in surefire reports and in terminal it is trimmed. **Is there any better solution ?**

My another concern is whether I can use for almost every exception ```IllegalArgumentException``` type. I was thinking about introducing my own exception hierarchy. Like parent ```GrapheneEnricherException``` and his subclasses ```PageFragmenEnricherException``` and ```PageObjectEnricherException```. It will be more readable I think and also it better encapsulates inner implementation. **What do you think it is worth trying** ?

Thanks in advance for you insight.