[jira] Resolved: (AVRO-138) Poor network connection blocks Java unit-tests

["Doug Cutting (JIRA)" <ji...@apache.org>]

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

Doug Cutting resolved AVRO-138.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0
         Assignee: Thiruvalluvan M. G.

Yes, I've been meaning to do something like this for a while.  A big advantage from my point of view is not just working offline, but that running a test with -Dtestcase= now takes only five seconds, greatly shortening the debug loop.

I just committed this.  Thanks, Thiru!

> Poor network connection blocks Java unit-tests
> ----------------------------------------------
>
>                 Key: AVRO-138
>                 URL: https://issues.apache.org/jira/browse/AVRO-138
>             Project: Avro
>          Issue Type: Bug
>            Reporter: Thiruvalluvan M. G.
>            Assignee: Thiruvalluvan M. G.
>             Fix For: 1.2.0
>
>         Attachments: AVRO-138.patch
>
>
> The ant target _test-java_ compiles the test code, run checkstyle, builds javadoc and then runs the unit tests. With poor or no internet connection, javadoc fails because it's not able to access java.sun.com or jackson.codehaus.org. These are used to create links in documentation for the JRE and Jackson APIs.
> In the following patch, I create a new target _unit-test-java_ and make _test-java_ depend on it. With this the order of execution for _test-java_ is compile test code, run unit tests, run checkstyle and then build javadoc. When, someone wants to just run the unit-tests, he/she can use _unit-test-java_.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.