Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove old Groovy code related to AwaitilityTrait and AwaitilitySupport #73

Merged
merged 1 commit into from Jan 18, 2017

Conversation

pkubowicz
Copy link
Contributor

@pkubowicz pkubowicz commented Jan 18, 2017

AwaitilityGroovyBridge needs to be removed because depending on random factors
(class loading?) it can overwrite code added by AwaitilityExtensionModule and
cause non-bool closures to fail - this is reproduced by tests added in this commit.

AwaitilityTrait and AwaitilitySupport can be made empty as AwaitilityExtensionModule
does their work now. They are left only to prevent a breaking API change.

… AwaitilitySupport

AwaitilityGroovyBridge needs to be removed because depending on random factors
(class loading?) it can overwrite code added by AwaitilityExtensionModule and
cause non-bool closures to fail - this is reproduced by tests added in this commit.

AwaitilityTrait and AwaitilitySupport can be made empty as AwaitilityExtensionModule
does their work now. They are left only to prevent a breaking API change.
@pkubowicz pkubowicz changed the title [#71] Remove old Groovy code related to AwaitilityTrait and Awaitilit… Remove old Groovy code related to AwaitilityTrait and Awaitilit… Jan 18, 2017
@pkubowicz pkubowicz changed the title Remove old Groovy code related to AwaitilityTrait and Awaitilit… Remove old Groovy code related to AwaitilityTrait and AwaitilitySupport Jan 18, 2017
@johanhaleby johanhaleby merged commit c12224f into awaitility:master Jan 18, 2017
@johanhaleby
Copy link
Collaborator

Thanks again!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants