-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Broken OSGi bundle wiring and build #3844
Comments
pavelhoral
added a commit
to pavelhoral/flowable-engine
that referenced
this issue
Feb 8, 2024
pavelhoral
added a commit
to pavelhoral/flowable-engine
that referenced
this issue
Feb 8, 2024
pavelhoral
added a commit
to pavelhoral/flowable-engine
that referenced
this issue
Feb 8, 2024
pavelhoral
added a commit
to pavelhoral/flowable-engine
that referenced
this issue
Feb 8, 2024
filiphr
pushed a commit
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Current build on main is broken so I am creating this issue to have a place for a discussion how to tackle it. The issue is probably caused by recent changes that broke bundle wiring and introduced unwanted
Import-Package
declarations.One example of such package dependency (that gets picked up by bndtool) is
org.flowable.common.engine.impl.aot.FlowableMyBatisRuntimeHints
that uses classes fromorg.apache.ibatis.javassist.util.proxy
package that is not being exported by mybatis bundle.Expected behavior
OSGi bundles should not depend on non-OSGi packages and tests should pass.
Additional context
I am sure you are looking into this as well as this causes pipeline on main to fail. However as external person I wanted to have a place where I can write my own observations. Originally discussed here #3843 (comment) .
The text was updated successfully, but these errors were encountered: