[ARROW-16825] [Java] Inclusion of a git.properties resource in Arrow JARs causes confusion in Spring Boot applications

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 8.0.0
• Fix Version/s: 9.0.0
• Component/s: Java
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/32154
• Assignee: David Dali Susanibar Arce
• Reporter: Nils Breunese
• Created: 13/Jun/22 14:21
• Updated: 11/Jan/23 11:46
• Resolved: 12/Jul/22 20:03

Description

By default Spring Boot reads classpath:git.properties to get information about the Git repository of an application. However, Arrow JARs also include a resource called git.properties, and this can cause Spring Boot to read the information from one of the Arrow libraries instead of from the application. This was reported to Spring Boot as an issue, but the Spring Boot developers say that they cannot automatically distinguish the application Git properties from git.properties resources from dependencies.

Would you consider omitting git.properties from Arrow JARs in future releases or will Spring Boot users that (directly or indirectly) use Arrow need to work around this by letting git-commit-id-plugin generate the application Git properties in an alternative location and configuring Spring Boot to read the information from that alternative location (spring.info.git.location)? Of course other libraries could also cause this issue, but Arrow is the first and only library that I've encountered so far that publishes JARs with a git.properties resource in them.

It seems that the fact that Arrow JARs include git.properties resources also caused ARROW-6361.

Issue Links

• is related to: ARROW-6361 [Java] sbt docker publish fails due to Arrow dependecies
• links to: GitHub Pull Request #13578