aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David McLaughlin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AURORA-1951) UI build broken in gradle 4.2
Date Wed, 27 Sep 2017 17:25:00 GMT
David McLaughlin created AURORA-1951:
----------------------------------------

             Summary: UI build broken in gradle 4.2
                 Key: AURORA-1951
                 URL: https://issues.apache.org/jira/browse/AURORA-1951
             Project: Aurora
          Issue Type: Task
            Reporter: David McLaughlin
            Assignee: Bill Farner


The recent upgrade to gradle 4.2 has broken the previously working ui build. It was a bit
of a nightmare for me to get this working originally and unfortunately I don't have the bandwidth
to bisect the changelog to see what they've changed. 

Here is the symptom of a false positive result:
{noformat}
$ ./gradlew --rerun-tasks ui:lint

BUILD SUCCESSFUL in 8s
3 actionable tasks: 3 executed
apache-aurora$ cd ui
ui$ 
ui$ npm run lint

> apache-aurora@1.0.0 lint /Users/dmclaughlin/t/apache-aurora/ui
> eslint src/main/js --ext .js


/Users/dmclaughlin/t/apache-aurora/ui/src/main/js/components/Icon.js
  3:7  error  'test' is assigned a value but never used  no-unused-vars

✖ 1 problem (1 error, 0 warnings)
{noformat}

I'm not totally sure which version of Gradle causes the regression.

I also saw issues with changing files and Gradle still considering the task UP-TO-DATE. This
would cause false positives in other ways and general make it unpleasant to work in the UI.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message