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.

Sign up for GitHub

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

Jump to bottom

Consider transitive dependencies when resolving TestEngine #71

Closed
aalmiray opened this issue Mar 20, 2019 · 1 comment
Closed

Consider transitive dependencies when resolving TestEngine #71

aalmiray opened this issue Mar 20, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@aalmiray
Copy link
Contributor

The current approach checks testCompile and testImplementation configurations, but fails to recognize the test engine if it happens to be defined in compile or implementation.

This is the case when a project defines test support and the test engine is part of its public API and dependencies.
@tlinkowski tlinkowski added the bug Something isn't working label Aug 24, 2019
siordache added a commit to beryx/gradle-modules-plugin that referenced this issue Mar 21, 2021
@siordache
issue java9-modularity#71: Consider transitive dependencies when reso…
c412621 
…lving TestEngine
@siordache siordache mentioned this issue Mar 21, 2021
Merged
siordache added a commit that referenced this issue Mar 28, 2021
@siordache
Issue #71, #140, #172 (#180)
9b233dc 
* issue #140: Support gradle test fixtures
* issue #71: Consider transitive dependencies when resolving TestEngine
* issue #172: TestNG has the wrong module name for versions 7.0.0 and above
@big-andy-coates
Copy link
Collaborator

Should be fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aalmiray @big-andy-coates @tlinkowski