Skip to content

Conversation

fedinskiy
Copy link
Contributor

  • Take versions of dependencies from Quarkus Platform BOMs
  • Use platform-dependent version of quarkus-maven-plugin (required for work with RHBQ)
  • Drop deployment dependencies (it doesn't look like their usage affects the size of the build at all)

@fedinskiy fedinskiy requested a review from a team as a code owner September 2, 2025 13:08
- Take versions of dependencies from Quarkus BOMs
- Use platfrom-dependent version of qaurkus-maven-plugin (required for
  work with RHBQ)
- Drop deployment dependecies (it doesn't look like their usage affects the size
  of the build at all)
@geoand
Copy link
Collaborator

geoand commented Sep 2, 2025

I actually think that this change is not helpful for people coming to Quarkus LangChain4j for the samples.

@fedinskiy
Copy link
Contributor Author

@geoand could you elaborate? These poms are now much closer to ones generated by quarkus cli or maven plugin, and so are less surprising for users.

Copy link

quarkus-bot bot commented Sep 2, 2025

Status for workflow Build (on pull request)

This is the status report for running Build (on pull request) on commit d3bbfc0.

Failing Jobs

Status Name Step Failures Logs Raw logs
JVM tests - samples - Java 17 Run tests of samples with JDK 17 ⚠️ Check → Logs Raw logs
JVM tests - samples - Java 21 Run tests of samples with JDK 21 ⚠️ Check → Logs Raw logs
JVM tests - samples - Java 24 Run tests of samples with JDK 24 ⚠️ Check → Logs Raw logs

@geoand
Copy link
Collaborator

geoand commented Sep 2, 2025

I don't want the samples to be tied to the latest version on the Quarkus platform - I want them to always reflect the latest Quarkus LangChain4j version.

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