edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Created] (QUARKS-235) [gradle] AppServicesTest woes
Date Wed, 20 Jul 2016 16:04:20 GMT
Dale LaBossiere created QUARKS-235:

             Summary: [gradle] AppServicesTest woes
                 Key: QUARKS-235
                 URL: https://issues.apache.org/jira/browse/QUARKS-235
             Project: Quarks
          Issue Type: Bug
            Reporter: Dale LaBossiere

I may end up delivering a fix for this in the context of the rename-to-edgent work.

Even after picking up the merged PR-169 (AppServiceTest doesn't build),
the AppServicesTest ("gradle :providers:direct:test") fails constantly.   The gradle test
build / execution scripts lack some of the functionality present in the ant harness:

- edgent.test.root.dir isn't set
- api/topology/test.classes/quarks.api.topology.APPS.TEST.jar isn't created

Easy enough to set the first in <repo>/build.gradle
To deal with the differences in build artifact location, will also need something like:
     systemProperty 'edgent.test.classes.dir', "build/classes/test"
and tweak the test's generation of the jar path.

And need to update gradle with the analog of the APPS.TEST jar building present in api/topology/build.xml

FYI, in the shorter term, to see what other gradle test work may be necessary, in my workspace
I've added:
    systemProperty 'edgent.test.isGradle', "true"
and added an assumeTrue(!Boolean.getBoolean("edgent.test.isGradle");
to the test.

This message was sent by Atlassian JIRA

View raw message