Skip to content

Conversation

@rovarga
Copy link
Contributor

@rovarga rovarga commented Apr 24, 2025

Split karaf-bom into multiple parts, so users can pick their buy-in level.

rovarga added 5 commits April 25, 2025 00:01
osgi-core is non-modular, i.e. it has no Automatic-Module-Name
declaration.

This patches switches to using org.osgi.{dto,framework,resource,...},
which are provide this stability.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Split out the modular OSGi Core specification dependency parts into
karaf-bom-osgi, providing more modular dependency management.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Split out the modular OSGi Companion specification dependency parts
which are supported by the 'framework' feature into their own bom.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Split out the modular OSGi Companion specification dependency parts
which are supported by the 'standard' feature into their own bom.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
Split out the modular OSGi Companion specification dependency parts
which are supported by the 'enterprise' feature into their own bom.

Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
@jbonofre jbonofre self-requested a review April 25, 2025 08:18
@jbonofre
Copy link
Member

There's something wrong in version resolution with JDK20. I gonna try locally.

@mattrpav
Copy link
Contributor

mattrpav commented May 8, 2025

This probably should be Karaf 4.5.x or higher. Adding to 4.4.x would break existing users dependency management and packaging.

@jbonofre
Copy link
Member

jbonofre commented May 8, 2025

Yes definitely not for 4.4.x. Also I would like to evaluate that.

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.

3 participants