Splits nio project into two for eclipse build only #27939
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#27801 introduced a new gradle project
:libs:elasticsearch-niowhich creates cyclical project dependencies when importing the projects into Eclipse.This change applies the same trick as we have for the core project where, and building for Eclipse, splits the
:libs:elasticsearch-nioproject into:libs:elasticsearch-niowhich points tosrc/mainand:libs:elasticsearch-nio-testswhich points tosrc/test. This prevents cyclical project dependencies in Eclipse arising from the fact that eclipse does not separate compile/runtime dependencies from test dependencies.