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.

Comment From: mhalbritter

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

Comment From: 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

Comment From: mhalbritter

Thanks @hdsfh , it's all yours.

Comment From: Lublanski

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