Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 13 Jun 2012 12:25:42 +0000 (UTC)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1403713236.12411.1339590342887.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (DERBY-5815) Add replicationTests.ReplicationSuite
 to junit-core ant target
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Kristian Waagan created DERBY-5815:
--------------------------------------

             Summary: Add replicationTests.ReplicationSuite to junit-core ant target
                 Key: DERBY-5815
                 URL: https://issues.apache.org/jira/browse/DERBY-5815
             Project: Derby
          Issue Type: Improvement
          Components: Test
    Affects Versions: 10.10.0.0
            Reporter: Kristian Waagan
            Assignee: Kristian Waagan
            Priority: Trivial


The replication tests aren't run as part of the junit-core ant target (nor in any of the other relevant targets).
I suggest adding the suite such that is is run as part of the top-level ant targets for testing Derby.

Note that it would have been simpler to simply run suites.All, but the special logic for JDBC 4 code may still be relevant for some platforms (JSR169). It is also nice to get some more feedback as the test cycle proceeds. The downside of not using suites.All is that we may forget adding new suites to the ant target(s), but we're adding so few new suites that it shouldn't be much of a problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira