-
Notifications
You must be signed in to change notification settings - Fork 18
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
FISH-786: Support both MP 3.3. and 4.0+ in OSGi #115
Conversation
Don't export MP packages. Allow to import MP Config from version 1.4 (MP 3.3) to 2.0+ (MP 4.0+) This is needed to integrate to the latest Payara Enterprise
openid/pom.xml
Outdated
*;resolution:=optional, org.eclipse.microprofile.config;v | ||
ersion="[1.0,3)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, the end of the line was too heavy and it dropped ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed that. I'll these on the same line.
oauth2/pom.xml
Outdated
<Import-Package> | ||
!org.eclipse.microprofile.*, | ||
org.eclipse.microprofile.config;version="[1.0,3)", | ||
* | ||
</Import-Package> | ||
<Export-Package> | ||
!org.eclipse.microprofile.*, | ||
fish.payara.security.oauth2.* | ||
</Export-Package> | ||
</instructions> | ||
<excludeDependencies>microprofile,microprofile-config-api</excludeDependencies> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are all of these necessary? In theory only *
and the rule for config package should be necessary, and only for imports.
Exports and excludeDependencies are not needed (I didn't try though).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. In the end it's enough to place the config package in import before the microprofile and * imports. When I added it to the end of the list, it was being ignored because the packages were handled by the previous rules.
d622030
to
4485170
Compare
Don't export MP packages. Allow to import MP Config
from version 1.4 (MP 3.3) to 2.0+ (MP 4.0+)
This is needed to integrate to the latest Payara Enterprise.