Fix brew warnings for Spring Boot CLI

[mhalbritter]

When running brew with HOMEBREW_DEVELOPER=true, these warnings appear when running brew install spring-boot:

::warning::JARs were installed to "/home/linuxbrew/.linuxbrew/opt/spring-boot/lib". Installing JARs to "lib" can cause conflicts between packages.
For Java software, it is typically better for the formula to install to "libexec" and then symlink or wrap binaries into "bin".
See formulae 'activemq', 'jruby', etc. for examples.The offending files are:
- /home/linuxbrew/.linuxbrew/opt/spring-boot/lib/spring-boot-cli-3.4.9-SNAPSHOT.jar

When HOMEBREW_DEVELOPER is not set, those warnings are not shown.

[mhalbritter]

This is currently breaking our verification tests: https://github.com/spring-projects/spring-boot/actions/runs/17035370141/job/48287479524

[hdsfh]

Hi @mhalbritter ,

I'd like to try to help fix this brew warning issue for Spring Boot CLI!
First, I will reproduce the problem: run it as described HOMEBREW_DEVELOPER=true brew install spring-boot，Confirm whether the warning appears steadily.
Then，Analysis the reason of warning —— It seems to be the JAR installation path（lib directory）It does not comply with Homebrew's recommended specifications for Java software (it is suggested to use libexec for symbolic links).
If it is necessary to modify the code repository (such as the CLI module of Spring Boot) or Homebrew Formula, I will：
Fork relevant deposity；
Adjust the path configuration and symbolic link script to ensure normal functionality and the disappearance of warnings;
Write tests (if there is a verification test stage) to ensure that modifications do not introduce new problems.
I would like to confirm:
Does the fix of this Issue mainly involve the CLI installation logic of the Spring Boot repository or the adjustment of the Homebrew Formula?
Are there any known code locations or configuration files that can be prioritized for investigation?
I will start debugging as soon as possible. If there is any progress or question, I will keep in touch at any time.
Thanks!
CherryBomb

[mhalbritter]

Thanks @hdsfh , it's all yours.

[Lublanski]

@mhalbritter I opened the fix, I'm waiting for the review.

[mhalbritter]

Thank you! I'll add it on my list.

[mhalbritter]

Hello @hdsfh , how's it going with the Brew CLI?

[rpjicond]

Hi @hdsfh,

Great analysis on this issue. The proposed solution to install the CLI JARs into libexec and use a wrapper script in bin seems like the correct approach according to Homebrew's best practices.

I have experience with both the Spring ecosystem and Shell scripting for package management, and I would be very excited to help fix this. I see you are assigned to the issue. If you've already started working on a fix, that's fantastic. However, if you've run into any blockers or find that you don't have the time to continue, I would be happy to take over and submit a pull request.

Please let us know your status when you get a chance.

Thank you!

[Lublanski]

Hi, I think I've fixed the issue, but I opened the PR in the wrong repository. I'll open a new PR for the correct repository and wait for review. Sincerely Lublanski. Em qua., 1 de out. de 2025 às 08:42, Ronaldo Paulino Jiconda < ***@***.***> escreveu:

…

*rpjicond* left a comment (spring-projects/spring-boot#46866) <#46866 (comment)> Hi @hdsfh <https://github.com/hdsfh>, Great analysis on this issue. The proposed solution to install the CLI JARs into libexec and use a wrapper script in bin seems like the correct approach according to Homebrew's best practices. I have experience with both the Spring ecosystem and Shell scripting for package management, and I would be very excited to help fix this. I see you are assigned to the issue. If you've already started working on a fix, that's fantastic. However, if you've run into any blockers or find that you don't have the time to continue, I would be happy to take over and submit a pull request. Please let us know your status when you get a chance. Thank you! — Reply to this email directly, view it on GitHub <#46866 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN54U5L5TAX4FNMMAB3U7S33VO4Y5AVCNFSM6AAAAACEEOFDNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNJVHEZTIMBZG4> . You are receiving this because you commented.Message ID: ***@***.***>

[wilkinsona]

@Lublanski please wait for a response from @hdsfh before doing so. They offered to contribute a fix a few weeks ago and the issue is assigned to them.

[Lublanski]

@wilkinsona Oh, I see, I apologize. I thought anyone could open the PR at any time.

Anyway, from what I tested, I was able to fix the issue.

@hdsfh, Have you started working on the fix? I'm happy to try to help you.

[snicoll]

We haven't heard from @hdsfh for a while so I am going to unassign them. @Lublanski are you still interested to contribute a fix for this? If so please go ahead and submit a PR. I'd appreciate an answer either way so that we can deal with it ourselves if necessary. Thanks!