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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2009/01/15 18:18:59 UTC

[jira] Created: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Remove dependency of junit targets on deprecated jdk16 variable
---------------------------------------------------------------

                 Key: DERBY-4022
                 URL: https://issues.apache.org/jira/browse/DERBY-4022
             Project: Derby
          Issue Type: Improvement
          Components: Build tools
    Affects Versions: 10.5.0.0
            Reporter: Rick Hillegas


The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Updated: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-4022:
---------------------------------

    Derby Info: [Patch Available]

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Updated: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas updated DERBY-4022:
---------------------------------

    Attachment: derby-4022-01-aa-junitVSjdk16.diff

Attaching derby-4022-01-aa-junitVSjdk16.diff. This patch removes the dependency of the junit JDBC4 test target on the deprecated jdk16 variable. Makes the following changes:

1) Removes the final mention of jdk16 in the master build.xml file.

2) Makes the junit-jdbc4 target depend on whether the VM level is at least Java 6.

Note that this involves a behavioral change from the previous situation. Previously, you could run the ant targets in a Java 5 environment and the JDBC4 tests would run (on Java 6) if you set jdk16 correctly. Now you only get the JDBC4 tests if your environment is at least Java 6. This seems like a straightforward solution to deprecating jdk16 and ought to fit the usage of most people. However, it may not fit the usage of some developers. If this is an intolerable change, then we may want to consider preserving the jdk16 variable for use only by the tests.

If this solution does seem acceptable, then we probably need to update the testing documentation to remove references to jdk16.


Touches the following file:

M      build.xml


> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Commented: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664530#action_12664530 ] 

Rick Hillegas commented on DERBY-4022:
--------------------------------------

If there are no objections to the behavioral change, then I propose to check this in next Tuesday.

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Commented: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665563#action_12665563 ] 

Rick Hillegas commented on DERBY-4022:
--------------------------------------

Committed derby-4022-01-aa-junitVSjdk16.diff at subversion revision 736106.

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Assigned: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas reassigned DERBY-4022:
------------------------------------

    Assignee: Rick Hillegas

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Closed: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas closed DERBY-4022.
--------------------------------


> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.1.1
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.5.1.1
>
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Updated: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Myrna van Lunteren updated DERBY-4022:
--------------------------------------

    Fix Version/s: 10.5.0.0

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>             Fix For: 10.5.0.0
>
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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


[jira] Resolved: (DERBY-4022) Remove dependency of junit targets on deprecated jdk16 variable

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Hillegas resolved DERBY-4022.
----------------------------------

    Resolution: Fixed

> Remove dependency of junit targets on deprecated jdk16 variable
> ---------------------------------------------------------------
>
>                 Key: DERBY-4022
>                 URL: https://issues.apache.org/jira/browse/DERBY-4022
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.5.0.0
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-4022-01-aa-junitVSjdk16.diff
>
>
> The junit target for running the jdbc4 tests depends on the jdk16 variable being set in your ant.properties. For the build, this variable has been deprecated. We should be able to make the jdbc4 tests depend on whether the environment is Java 6 instead.

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