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

Review extensions' dependencies chains #56

Closed
lburgazzoli opened this issue Jul 10, 2019 · 2 comments · Fixed by #59
Closed

Review extensions' dependencies chains #56

lburgazzoli opened this issue Jul 10, 2019 · 2 comments · Fixed by #59
Assignees

Comments

@lburgazzoli
Copy link
Contributor

i.e.

  • deployments should depend on camel-quarkus-code-deployment
  • deployments should not depends on arc-deployment and quarkus-deployment as is should be transitively provided by camel-quarkus-code-deployment
@lburgazzoli lburgazzoli self-assigned this Jul 10, 2019
@ppalaga
Copy link
Contributor

ppalaga commented Jul 10, 2019

I vote for enforcing things like this via a groovy script, enforcer plugin or similar automatic solution. Our ultimate goal is to have extensions for most Camel components and the bigger the number of extensions gets the harder it will be to keep things like this under control.

@lburgazzoli
Copy link
Contributor Author

I'll open a new issue for that

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 a pull request may close this issue.

2 participants