Skip to content

Dependency management for JavaBeans Activation Framework is incomplete #17062

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
Closed
wilkinsona opened this issue Jun 5, 2019 · 1 comment
Closed

Dependency management for JavaBeans Activation Framework is incomplete #17062

wilkinsona opened this issue Jun 5, 2019 · 1 comment
Assignees
@wilkinsona
Labels
type: bug A general bug
Milestone
2.1.6

Comments

@wilkinsona
Copy link
Member

We manage the API dependency but not the implementation. Both should be managed as, while they have different group IDs, they are developed as part of the same project and are tagged and released together.
@wilkinsona wilkinsona added the type: bug A general bug label Jun 5, 2019
@wilkinsona wilkinsona added this to the 2.1.x milestone Jun 5, 2019
@wilkinsona wilkinsona mentioned this issue Jun 5, 2019
Closed
@ielatif
Copy link
Contributor

ielatif commented Jun 5, 2019

Interesting discussions about this topic from eclipse-ee4j projects jakarta.activation-api should not be used at runtime and Substitute jakarta.activation-api with jakarta.activation

@wilkinsona wilkinsona modified the milestones: 2.1.x, 2.1.6 Jun 17, 2019
@wilkinsona wilkinsona self-assigned this Jun 17, 2019
@wilkinsona wilkinsona mentioned this issue Jun 17, 2019
Closed
@wilkinsona wilkinsona mentioned this issue Nov 8, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wilkinsona wilkinsona

Labels
type: bug A general bug
Projects
None yet
Milestone
2.1.6
Development

No branches or pull requests
2 participants
@ielatif @wilkinsona