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

Merge camel-quarkus-bom-deployment into camel-quarkus-bom #1413

Closed
lburgazzoli opened this issue Jun 23, 2020 · 6 comments
Closed

Merge camel-quarkus-bom-deployment into camel-quarkus-bom #1413

lburgazzoli opened this issue Jun 23, 2020 · 6 comments
Assignees
Labels
question Further information is requested
Milestone

Comments

@lburgazzoli
Copy link
Contributor

Quarkus will probably deprecate quarkus-bom-deployment and merge its content into quarkus-bom [1], should we do the same ?

[1] quarkusio/quarkus#10182

@lburgazzoli lburgazzoli added the question Further information is requested label Jun 23, 2020
@ppalaga
Copy link
Contributor

ppalaga commented Jun 23, 2020

Let's wait for the result of the discussion on quarkus-dev ML.

@ppalaga
Copy link
Contributor

ppalaga commented Jun 25, 2020

The chance that the deployment BOM is going to survive is close to zero now.

@ppalaga ppalaga self-assigned this Jun 25, 2020
@ppalaga
Copy link
Contributor

ppalaga commented Jun 25, 2020

Quarkus is keeping their deployment BOM as an alias of their runtime BOM.

I guess we can remove the deployment BOM, because we are not assuming any third party depends on it?

@lburgazzoli
Copy link
Contributor Author

We are not yet a 1.0 so - IMHO - we can safely do such kind of changes

@ppalaga
Copy link
Contributor

ppalaga commented Jul 15, 2020

Fixed via 4810732

@ppalaga ppalaga closed this as completed Jul 15, 2020
@ppalaga ppalaga added this to the 1.0.0 milestone Aug 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants