You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2012/06/13 14:25:42 UTC
[jira] [Created] (DERBY-5815) Add replicationTests.ReplicationSuite
to junit-core ant target
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
[jira] [Commented] (DERBY-5815) Add
replicationTests.ReplicationSuite to junit-core ant target
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294920#comment-13294920 ]
Knut Anders Hatlen commented on DERBY-5815:
-------------------------------------------
The patch looks good to me. +1
> 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
> Attachments: derby-5815-1a-add_replication_suite.diff
>
>
> 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
[jira] [Closed] (DERBY-5815) Add replicationTests.ReplicationSuite
to junit-core ant target
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-5815.
----------------------------------
Closing issue.
> 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
> Fix For: 10.10.0.0
>
> Attachments: derby-5815-1a-add_replication_suite.diff
>
>
> 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
[jira] [Resolved] (DERBY-5815) Add
replicationTests.ReplicationSuite to junit-core ant target
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-5815.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Thanks, Knut Anders.
Committed patch 1a to trunk with revision 1350166.
> 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
> Fix For: 10.10.0.0
>
> Attachments: derby-5815-1a-add_replication_suite.diff
>
>
> 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
[jira] [Updated] (DERBY-5815) Add replicationTests.ReplicationSuite
to junit-core ant target
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5815:
-----------------------------------
Attachment: derby-5815-1a-add_replication_suite.diff
Attaching patch 1a, adding the replication suite to the junit-core ant target.
> 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
> Attachments: derby-5815-1a-add_replication_suite.diff
>
>
> 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