You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2021/05/07 16:59:42 UTC

[GitHub] [lucene] gautamworah96 commented on pull request #108: LUCENE-9897 Change dependency checking mechanism to use gradle checksum verification

gautamworah96 commented on pull request #108:
URL: https://github.com/apache/lucene/pull/108#issuecomment-834622966


   Some closing notes: We found the current gradle checksum verification functionality unsuitable for our use case.
   The current functionality records all dependencies (plugins et al) for a given configuration that was used to generate the `verification-metadata.xml` file. However, it fails builds on other configurations that use other external dependencies.
   
   When could this possibly work? If gradle were to check dependencies only when the task that was used to generate the metadata file is executed, it would allow developers to safely create more configurations (with other dependencies) without the restriction of adding them to the global metadata file.


-- 
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:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org