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] [Resolved] (EDGENT-390) improve test with java7 doc
Date Tue, 28 Feb 2017 13:53:51 GMT

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

Dale LaBossiere resolved EDGENT-390.
------------------------------------
    Resolution: Fixed

resolved via https://github.com/apache/incubator-edgent/pull/292

> improve test with java7 doc
> ---------------------------
>
>                 Key: EDGENT-390
>                 URL: https://issues.apache.org/jira/browse/EDGENT-390
>             Project: Edgent
>          Issue Type: Task
>          Components: Documentation
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>            Priority: Minor
>
> The steps for testing with java7 are described [here|https://github.com/apache/incubator-edgent/blob/master/DEVELOPMENT.md#testing-edgent-with-java7].
> If the tests and reports are run after running the normal java8 tests then the test report
isn't helpful as it contains all of the java8 test results and you can't identify which were
updated with java7 results.
> So before (or after) running test7Compile do "gw cleanTest" then "gw reports" (which
will generate an report set).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message