Hi Charles,

The plan is to release 3.0 which will contain the fix that's already on
master early next week. I'm not planning to make any changes between now
and the release so you might as well use 3.0-SNAPSHOT until then, see
http://www.gebish.org/manual/current/#snapshot-repository. Be warned that
there is a number of breaking changes in 3.0, see
http://www.gebish.org/manual/snapshot/#breaking-changes.

Regards,
Marcin

On Tue, May 21, 2019 at 10:11 PM Charles Moga <[email protected]>
wrote:

> Hello Marcin,
> Any idea when this will be released? I am facing this same error and I
> cannot get to the bottom at all of the root cause. I am currently on 2.3.1.
>
> Regards
> Charles
>
> On Sunday, 14 April 2019 19:58:34 UTC+1, Marcin Erdmann wrote:
>>
>> Thanks for your email and the report of the issue you've encountered. The
>> root exception, also referred to as cause is ignored in this case and not
>> passed on in the constructor of UnableToLoadException:
>> https://github.com/geb/geb/blob/a948be381fd2e25b5b170a421a555b8bd90128d0/module/geb-core/src/main/groovy/geb/error/UnableToLoadException.groovy#L24.
>> If it was passed on to the super constructor then you'd see its message and
>> stacktrace would be included in your original stacktrace. This is clearly a
>> bug which I've recently accidentally introduced and not the intended
>> behaviour so I've created an issue for it:
>> https://github.com/geb/issues/issues/572.
>>
>> On Fri, Apr 12, 2019 at 2:26 PM <[email protected]> wrote:
>>
>>> I found the problem.
>>> It was related to an exception that I throw myself in GebConfig.groovy,
>>> if some parameter are not provided, which might happen as a result of not
>>> doing a clean build.
>>> I was confused because it did not print the message of that root
>>> exception, which would've helped greatly.
>>> I only got to read it when I remote debugged the process, and inspect
>>> the throwable in this line:
>>>
>>> ConfigurationLoader.groovy, line 304 - 306:
>>>
>>> } catch (Throwable e) {
>>>     throw new UnableToLoadException(source, slurper.environment, e)
>>> }
>>>
>>>
>>> Is there a generic way to make Java/Gradle/Whatever print the message of
>>> "e" also?
>>>
>>> I tried exceptionFormat = 'full' in the Gradle Test task, but it didn't
>>> do anything for me.
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Geb User Mailing List" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/geb-user/962a50a9-69d3-48f7-a7e1-06f8736e9b6f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/geb-user/962a50a9-69d3-48f7-a7e1-06f8736e9b6f%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Geb User Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/geb-user/a5602e2d-92d6-4187-b466-daea8290ece5%40googlegroups.com
> <https://groups.google.com/d/msgid/geb-user/a5602e2d-92d6-4187-b466-daea8290ece5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Geb 
User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/geb-user/CA%2B52dQRiqkXSdK3a%3DV1au4a0TZRn_YSJfiQbpF-_z5moOdsW4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to