[
https://issues.apache.org/jira/browse/LUCENE-6938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090608#comment-15090608
]
Uwe Schindler commented on LUCENE-6938:
---------------------------------------
bq. How about the main build gets the git hash and writes it to a temporary
property file. All other build phases can then just read that file and we are
done. Am I missing something?
Thats not good, because on git update it would not update that file unless you
do ant clean. The solution proposed before is easy, I will implement it later,
no worries. We have the infrastructure:
- a task will be added to common-build.xml that gets git hash and saves it in
property. This task has {{unless="property"}}
- property is added to the patternset of properties to pass down the sub-modules
- all submodules JAR tasks call the task as dependency. But if the upper builds
has already defined the property it is a no-op
No worries, I will take care! For now just use the approach we had with
Subversion.
> Convert build to work with Git rather than SVN.
> -----------------------------------------------
>
> Key: LUCENE-6938
> URL: https://issues.apache.org/jira/browse/LUCENE-6938
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Mark Miller
> Assignee: Mark Miller
> Attachments: LUCENE-6938.patch
>
>
> We assume an SVN checkout in parts of our build and will need to move to
> assuming a Git checkout.
> Patches against https://github.com/dweiss/lucene-solr-svn2git from
> LUCENE-6933.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
