Skip to content

Fix cyclic dependency between xpack-core and license-tools modules #41497

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

Closed
martijnvg opened this issue Apr 24, 2019 · 4 comments
Closed

Fix cyclic dependency between xpack-core and license-tools modules #41497

martijnvg opened this issue Apr 24, 2019 · 4 comments
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@martijnvg
Copy link
Member

Currently xpack-core module depends on the license-tools module and the license-tools module depends on xpack-core module.

I think to remove the cyclic dependency, the org.elasticsearch.license.licensor.LicenseSigner class should be moved from license-tools to xpack-core; then the xpack-core will no longer need to depend on license-tools?

Originates from #41064.

@martijnvg martijnvg added the :Delivery/Build Build or test infrastructure label Apr 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@alpar-t
Copy link
Contributor

alpar-t commented Sep 5, 2019

This is a cyclic dependency only in eclipse terms that does not distinguish between main and test dependencies. x-pack tests depend on license-tools.
This will no longer be relevant if #44075 merges.

@rjernst rjernst added the Team:Core/Infra Meta label for core/infra team label May 4, 2020
@mark-vieira mark-vieira added Team:Delivery Meta label for Delivery team and removed Team:Core/Infra Meta label for core/infra team labels Nov 11, 2020
@mark-vieira
Copy link
Contributor

@nik9000 is this still a concern or is Eclipse with Buildship able to cope with this now?

@nik9000
Copy link
Member

nik9000 commented Dec 21, 2020

Its now part of our standard Eclipse configuration to switch loops in the dependencies from build failures to build warnings. Its a manual step you have to do after importing the project. So, yeah, we can ignore this. Its pretty low down the list of things weird about eclipse.

@nik9000 nik9000 closed this as completed Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Development

No branches or pull requests

6 participants