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

Classifications Exports #133

Closed
InCadence opened this issue Feb 27, 2019 · 6 comments
Closed

Classifications Exports #133

InCadence opened this issue Feb 27, 2019 · 6 comments
Assignees
Labels

Comments

@InCadence
Copy link
Owner

Coalesce Core is exporting the classification packages.

@bytemedwb
Copy link
Collaborator

So what makes this a bug?

@dclemenzi
Copy link
Collaborator

coalesce-classification and coalesce-core are exporting the same package with the same version. Therefore depending on which bundle the classes are imported from will determine the signature and make it incompatible with bundles loading the package from the other.

@dclemenzi
Copy link
Collaborator

This has not been seen on our project because we are not using the CAPCO markings. But Matt experienced this issue when attempting to upgrade their version.

@dclemenzi
Copy link
Collaborator

Only affects applications running in Karaf or other OSGi environments.

@bytemedwb
Copy link
Collaborator

bytemedwb commented Feb 27, 2019 via email

@dclemenzi
Copy link
Collaborator

We don't ... the maven-bundle-plugin will shade packages that are explicitly exported. Therefore when we explicitly tell it to export ${project.groupId}.common.* this also includes ${project.groupId}.common.classification which is a dependency. So the fix is to remove the wild card and only list the packages included in coalesce-core.

InCadence added a commit that referenced this issue Feb 27, 2019
dclemenzi added a commit that referenced this issue Mar 2, 2019
… StringHelper in coalesce-core resolved the issue but this needs to be looked into.
dclemenzi added a commit that referenced this issue Mar 8, 2019
… StringHelper in coalesce-core resolved the issue but this needs to be looked into.
dclemenzi added a commit that referenced this issue Mar 15, 2019
… StringHelper in coalesce-core resolved the issue but this needs to be looked into.
dclemenzi added a commit that referenced this issue Mar 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants