[ 
https://issues.apache.org/jira/browse/ARROW-16825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17554270#comment-17554270
 ] 

Kouhei Sutou commented on ARROW-16825:
--------------------------------------

[~sphillips] Do you remember why our {{.jar}} provide {{git.properties}}? It 
seems that your initial commit 
https://github.com/apache/arrow/commit/fa5f0299f046c46e1b2f671e5e3b4f1956522711#diff-d8225ebcfc11b480a6e4f54e183b67c3ead51635a167c106d928c2abf1f9ef66R233-R274
 / ARROW-1 includes it.

> Inclusion of a git.properties resource in Arrow JARs causes confusion in 
> Spring Boot applications
> -------------------------------------------------------------------------------------------------
>
>                 Key: ARROW-16825
>                 URL: https://issues.apache.org/jira/browse/ARROW-16825
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Java
>    Affects Versions: 8.0.0
>            Reporter: Nils Breunese
>            Priority: Minor
>
> 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|https://github.com/spring-projects/spring-boot/issues/18137], 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.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to