[
https://issues.jboss.org/browse/ARQ-1567?page=com.atlassian.jira.plugin.s...
]
Karel Piwko commented on ARQ-1567:
----------------------------------
[~smikloso], would it be possible to check system property java.home as well? While this
might point to JRE in some cases, it might make setup easier.
Explain validation errors in more depth
---------------------------------------
Key: ARQ-1567
URL:
https://issues.jboss.org/browse/ARQ-1567
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Extension - Droidium
Affects Versions: droidium_1.0.0.Alpha2
Reporter: Stefan Miklosovic
In many cases, it is not sufficient to provide a user just with stack trace when
something goes wrong, for example, from this one:
{code}
java.lang.IllegalStateException: Directory to check against readability is null object or
empty string.
at
org.arquillian.droidium.container.configuration.Validate.notNullOrEmpty(Validate.java:98)
at
org.arquillian.droidium.container.configuration.Validate.isReadableDirectory(Validate.java:147)
at
org.arquillian.droidium.container.configuration.AndroidSDK.<init>(AndroidSDK.java:189)
at
org.arquillian.droidium.container.AndroidDeployableContainer.setup(AndroidDeployableContainer.java:153)
{code}
It basically says that user does not have specified JAVA_HOME but he can not know that
without looking into sources which is *totally* not desired.
Review all crucial configuration properties and its setters / getters and be sure that
when it fails user knows whats going on.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira