[
https://issues.apache.org/jira/browse/ARROW-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Mayi updated ARROW-1239:
-------------------------------
Description:
Currently used version of the git-commit-id-plugin maven plugin (2.1.9) doesn't
work with recent git structures. This is for majority of the users not
manifested since Arrow has the java maven root in the project subdirectory
({{/java}}) instead of top level so this plugin normally doesn't kick in if
maven is executed from the subdirectory (usual case - ie {{cd java; mvn
install}} - works fine) as the plugin doesn't see the {{.git}} directory but it
does kick in and fail if executed from the main arrow top level dir as {{mvn -f
java/pom.xml install}} (where the {{.git}} sits):
{quote}
$ mvn -f java/pom.xml package
...
[ERROR] Failed to execute goal
pl.project13.maven:git-commit-id-plugin:2.1.9:revision (for-jars) on project
arrow-java-root: Execution for-jars of goal
pl.project13.maven:git-commit-id-plugin:2.1.9:revision failed: Bare Repository
has neither a working tree, nor an index -> [Help 1]
{quote}
Simple fix is upgrading the plugin to recent version (the minimal working
version appears to be 2.1.13).
This is required for seamless integration with Jenkins (ARROW-1234).
was:
Currently used version of the git-commit-id-plugin maven plugin (2.1.9) doesn't
work with recent git structures. This is for majority of the users not
manifested since Arrow has the java maven root in the project subdirectory
({{/java}}) instead of top level so this plugin normally doesn't kick in if
maven is executed from the subdirectory (usual case - ie {{cd java; mvn
install}} - works fine) as the plugin doesn see the {{.git}} directory but it
does kick in and fail if executed from the main arrow top level dir as {{mvn -f
java/pom.xml install}} (where the {{.git}} sits):
{quote}
$ mvn -f java/pom.xml package
...
[ERROR] Failed to execute goal
pl.project13.maven:git-commit-id-plugin:2.1.9:revision (for-jars) on project
arrow-java-root: Execution for-jars of goal
pl.project13.maven:git-commit-id-plugin:2.1.9:revision failed: Bare Repository
has neither a working tree, nor an index -> [Help 1]
{quote}
Simple fix is upgrading the plugin to recent version (the minimal working
version appears to be 2.1.13).
> issue with current version of git-commit-id-plugin
> ---------------------------------------------------
>
> Key: ARROW-1239
> URL: https://issues.apache.org/jira/browse/ARROW-1239
> Project: Apache Arrow
> Issue Type: Bug
> Components: Java - Memory, Java - Vectors
> Environment: maven
> Reporter: Antony Mayi
> Assignee: Antony Mayi
> Fix For: 0.5.0
>
>
> Currently used version of the git-commit-id-plugin maven plugin (2.1.9)
> doesn't work with recent git structures. This is for majority of the users
> not manifested since Arrow has the java maven root in the project
> subdirectory ({{/java}}) instead of top level so this plugin normally
> doesn't kick in if maven is executed from the subdirectory (usual case - ie
> {{cd java; mvn install}} - works fine) as the plugin doesn't see the {{.git}}
> directory but it does kick in and fail if executed from the main arrow top
> level dir as {{mvn -f java/pom.xml install}} (where the {{.git}} sits):
> {quote}
> $ mvn -f java/pom.xml package
> ...
> [ERROR] Failed to execute goal
> pl.project13.maven:git-commit-id-plugin:2.1.9:revision (for-jars) on project
> arrow-java-root: Execution for-jars of goal
> pl.project13.maven:git-commit-id-plugin:2.1.9:revision failed: Bare
> Repository has neither a working tree, nor an index -> [Help 1]
> {quote}
> Simple fix is upgrading the plugin to recent version (the minimal working
> version appears to be 2.1.13).
> This is required for seamless integration with Jenkins (ARROW-1234).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)