Mailing-List: contact river-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Message-ID: <12829863.187951284495634981.JavaMail.jira@thor>
Date: Tue, 14 Sep 2010 16:20:34 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: river-commits@incubator.apache.org
Subject: [jira] Commented: (RIVER-301) Move the QA framework donated by Sun
 inside the jtsk trunk and integrate into build process
In-Reply-To: <850004628.1228755164435.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/RIVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909427#action_12909427 ] 

Hudson commented on RIVER-301:
------------------------------

Integrated in River-trunk #321 (See [https://hudson.apache.org/hudson/job/River-trunk/321/])
    RIVER-301: add "lookupservice" category to list of QA tests to run by Hudson


> Move the QA framework donated by Sun inside the jtsk trunk and integrate into build process
> -------------------------------------------------------------------------------------------
>
>                 Key: RIVER-301
>                 URL: https://issues.apache.org/jira/browse/RIVER-301
>             Project: River
>          Issue Type: Task
>          Components: other
>    Affects Versions: AR3
>            Reporter: Tom Hobbs
>            Assignee: Jonathan Costers
>         Attachments: integrationtest.xml, RIVER-301-JC-5.1.patch, RIVER-301-JC-6.0.patch.tar.gz, RIVER-301.patch, RIVER-301.patch, River-301.patch.zip, River-build-qa5.patch
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> The tests donated by SUN live in their own source project and are runnable in a format that is unfriendly towards IDEs and new developers to the River project.
> This is the proposal to move the test code, mostly unmodified, into the main source directory whilst shoe-horning it into JUnit 3.  This will allow it to be easily viewable and runnable.  Such a structure will also reduce the code-compile-test cycle since no JARs will have to be created in the middle of the cycle and no long command-line incantations.

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