[jira] [Resolved] (LUCENE-9780) Only validate JARs for tasks that are enabled.

["Houston Putman (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LUCENE-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Houston Putman resolved LUCENE-9780.
------------------------------------
    Fix Version/s: master (9.0)
         Assignee: Houston Putman
       Resolution: Fixed

> Only validate JARs for tasks that are enabled.
> ----------------------------------------------
>
>                 Key: LUCENE-9780
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9780
>             Project: Lucene - Core
>          Issue Type: Improvement
>    Affects Versions: master (9.0)
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>             Fix For: master (9.0)
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently if you disable parts of the build, such as the tasks in {{solr-ref-guide}}, the {{checkDanglingLicenseFiles}} task can fail. This is because if all tasks for a module are disabled, then the {{jarInfos}} task will be disabled, resulting in a missing {{jarInfos}} property.
> I understand this isn't a normal use case for the gradle check functionality, but because you can't build the {{solr-ref-guide}} with proxy repos, it's necessary to disable the project when trying to build in a restricted environment. (The solr-ref-guide is meant to be ignored from the Licenses checks, however it still fails when you disable tasks for the project.)
> An easy fix would be to merely check to make sure a task is enabled before trying to get the {{jarInfos}} for it's project.



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

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