Skip to content

HSEARCH-5356 Introduce the extended (platform) BOM #4712

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

marko-bekhta
Copy link
Member

https://hibernate.atlassian.net/browse/HSEARCH-5356


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.


@marko-bekhta marko-bekhta force-pushed the feat/HSEARCH-5356-Introduce-the-extended-platform-BOM branch 2 times, most recently from 8e929ac to 5f4284a Compare July 22, 2025 10:53
@marko-bekhta
Copy link
Member Author

hey @yrodiere 🙂 👋🏻 if you have the time ... I'd like your opinion on what's included in these platform poms 🫣 🙂

@marko-bekhta marko-bekhta force-pushed the feat/HSEARCH-5356-Introduce-the-extended-platform-BOM branch from 5f4284a to ef88840 Compare July 23, 2025 13:09
@marko-bekhta marko-bekhta force-pushed the feat/HSEARCH-5356-Introduce-the-extended-platform-BOM branch 4 times, most recently from b51821a to faec9f4 Compare July 24, 2025 15:10
Copy link
Member

@yrodiere yrodiere left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks. Some ideas below, but feel free to hate/ignore :)

Comment on lines 44 to 47
<!--
Hibernate Search artifacts listed explicitly as we cannot exclude some from the bom import,
and we want to skip the lucene-next ones for this pom to not mix different Lucene versions
-->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes me think you probably need a hibernate-search-next-bom too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one seems to work unexpectedly ok 😃
Since it does not manage Lucene directly each backend transitevely brings the version it wants as long as you do not use two lucene backends at the same time 😃

Comment on lines 140 to 200
<version>${version.bom.org.jberet}</version>
</dependency>
<dependency>
<groupId>org.jberet</groupId>
<artifactId>jberet-se</artifactId>
<version>${version.bom.org.jberet}</version>
</dependency>
<dependency>
<groupId>org.jberet</groupId>
<artifactId>test-deployment</artifactId>
<version>${version.bom.org.jberet}</version>
</dependency>

<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>archetype-lambda</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>aws-sdk-java</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>bundle-logging-bridge</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>bundle-sdk</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>bundle</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>core</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>crt-core</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>http-clients</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>metric-publishers</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>protocols</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>ruleset-testing-core</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>service-test-utils</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>services-custom</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>services</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>test-utils</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>third-party-slf4j-api</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>third-party</artifactId>
<version>${version.bom.software.amazon.awssdk}</version>
</dependency>
</dependencies>
</dependencyManagement>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make sense to avoid repetition by either:

  1. Importing the normal BOM and overriding just lucene dependencies? But then you'd be managing hibernate-search-backend-lucene (not next) even though it can't work with the managed version of Lucene.
  2. Importing a separate POM dedicated to just dependencies, not Hibernate Search artifacts, in both platform poms, and overriding the Lucene version here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Importing a separate POM dedicated to just dependencies, not Hibernate Search artifacts, in both platform poms, and overriding the Lucene version here?

this one would be nice yeah ... but I guess if we'd make some bom/platform-common we'd need to either publish it as well ... or don't publish but inline all the dependencies...

let me pull the common part and see if it would look better that way, and if so -- I'll just inline the dependencies, after all ... it is to manage dependencies and not to be read by a human on a daily basis 😁 🙈

@marko-bekhta marko-bekhta force-pushed the feat/HSEARCH-5356-Introduce-the-extended-platform-BOM branch from faec9f4 to 3f82c22 Compare July 25, 2025 19:59
@marko-bekhta marko-bekhta force-pushed the feat/HSEARCH-5356-Introduce-the-extended-platform-BOM branch from 3f82c22 to 0e302bd Compare July 25, 2025 20:41
Copy link

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.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy