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

LOGBACK-1728: Incorrect OSGi execution-environment requirements #640

Merged
merged 1 commit into from Mar 23, 2023

Conversation

HannesWell
Copy link
Contributor

@HannesWell HannesWell commented Mar 23, 2023

Remove the explicitly specified, but out dated, Bundle-RequiredExecutionEnvironment: JavaSE-1.6 and let the maven-bundle-plugin instead add a automatically computed ee-requirement (therefore remove the _noee instruction). This ensures the OSGi-ExecutionEnvironment metadata are always up to date.

Also remove all other explicitly configuration that can be derived automatically and is not necessary, like more Import-Package values or _failok. Some of the explicitly imported packages are not even referenced in the code.

Fixes https://jira.qos.ch/browse/LOGBACK-1728.

Remove the explicitly specified, but out dated,
'Bundle-RequiredExecutionEnvironment: JavaSE-1.6' entry and let the
maven-bundle-plugin instead add a automatically computed ee-requirement
(therefore remove the '_noee' instruction). This ensures the
OSGi-ExecutionEnvironment metadata are always up to date.

Remove all other explicitly configuration that can be derived
automatically and is not necessary, like more Import-Package values or
'_failok'.
Some of the explicitly imported packages are not even referenced in the
code.

Fixes https://jira.qos.ch/browse/LOGBACK-1728

Signed-off-by: Hannes Wellmann <wellmann.hannes1@gmx.net>
@HannesWell HannesWell changed the title Fix OSGi execution-environment requirements and simplify configuration LOGBACK-1728: Incorrect OSGi execution-environment requirements Mar 23, 2023
@HannesWell
Copy link
Contributor Author

@ceki would that also be interesting for the logback 1.3 branch? In general the same issue exists there are well, but the ee configuration probably has to be fine tuned a bit more due to the multi-release jar used for the modules-info.

@ceki ceki merged commit fccf9e6 into qos-ch:master Mar 23, 2023
1 check passed
@HannesWell HannesWell deleted the osgiEEConfig branch March 23, 2023 14:18
@ceki
Copy link
Member

ceki commented Mar 23, 2023

@HannesWell Yes, if not too much trouble, porting the PR to the 1.3 branch would be great.

@HannesWell
Copy link
Contributor Author

@HannesWell Yes, if not too much trouble, porting the PR to the 1.3 branch would be great.

I'm currently about to do that. Looks like the first attempt is already successful and it is less trouble than expected. :)

@HannesWell
Copy link
Contributor Author

@HannesWell Yes, if not too much trouble, porting the PR to the 1.3 branch would be great.

It was actually straight forward. Just created #641.

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 this pull request may close these issues.

None yet

2 participants