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

ASF GitHub Bot commented on KAFKA-8960:
---------------------------------------

ravowlga123 commented on pull request #7420: KAFKA-8960 Move Task 
determineCommitId in gradle.build to Project Level
URL: https://github.com/apache/kafka/pull/7420
 
 
   Currently, the gradle task determineCommitId is present twice in 
gradle.build, once in subproject clients and once in subproject streams. Task 
determineCommitId shall be moved to project-level such that both subprojects 
(and also other subprojects) can call it without being dependent on an 
implementation detail of another subproject. Ran the build after updating
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Move Task determineCommitId in gradle.build to Project Level
> ------------------------------------------------------------
>
>                 Key: KAFKA-8960
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8960
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, streams
>            Reporter: Bruno Cadonna
>            Assignee: Rabi Kumar K C
>            Priority: Minor
>              Labels: newbie
>
> Currently, the gradle task {{determineCommitId}} is present twice in 
> {{gradle.build}}, once in subproject {{clients}} and once in subproject 
> {{streams}}. Task {{determineCommitId}}  shall be moved to project-level such 
> that both subprojects (and also other subprojects) can call it without being 
> dependent on an implementation detail of another subproject.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to