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/08/30 14:47:07 UTC
[jira] [Created] (DERBY-5914) Incorrect list of compatible JRE
versions in client trace #2
Kristian Waagan created DERBY-5914:
--------------------------------------
Summary: Incorrect list of compatible JRE versions in client trace #2
Key: DERBY-5914
URL: https://issues.apache.org/jira/browse/DERBY-5914
Project: Derby
Issue Type: Bug
Components: Network Client
Affects Versions: 10.9.1.0, 10.10.0.0
Reporter: Kristian Waagan
Assignee: Kristian Waagan
Priority: Minor
The list of compatible JRE versions is out of sync again. It currently says 1.4, 1.5, and 1.6.
For trunk I believe we must remove 1.4, and we should add 1.7.
For 10.9, if we want to change it, I think we can keep 1.4? And 1.7 was out and supported before we released 10.9, right?
This issue was logged as DERBY-5078 the previous time it was out of sync.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DERBY-5914) Incorrect list of compatible JRE
versions in client trace #2
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-5914:
-----------------------------------
Attachment: derby-5914-1a-versions.diff
Attaching patch 1a, which removes 1.4 and adds 1.7 to the list of supported/compatible JRE versions.
Committed to trunk with revision 1392294.
> Incorrect list of compatible JRE versions in client trace #2
> ------------------------------------------------------------
>
> Key: DERBY-5914
> URL: https://issues.apache.org/jira/browse/DERBY-5914
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.9.1.0, 10.10.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Labels: derby_triage10_10
> Attachments: derby-5914-1a-versions.diff
>
>
> The list of compatible JRE versions is out of sync again. It currently says 1.4, 1.5, and 1.6.
> For trunk I believe we must remove 1.4, and we should add 1.7.
> For 10.9, if we want to change it, I think we can keep 1.4? And 1.7 was out and supported before we released 10.9, right?
> This issue was logged as DERBY-5078 the previous time it was out of sync.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DERBY-5914) Incorrect list of compatible JRE
versions in client trace #2
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-5914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan resolved DERBY-5914.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Given that this issue is about code used for tracing only, I don't plan to backport this.
Resolving issue.
> Incorrect list of compatible JRE versions in client trace #2
> ------------------------------------------------------------
>
> Key: DERBY-5914
> URL: https://issues.apache.org/jira/browse/DERBY-5914
> Project: Derby
> Issue Type: Bug
> Components: Network Client
> Affects Versions: 10.9.1.0, 10.10.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Labels: derby_triage10_10
> Fix For: 10.10.0.0
>
> Attachments: derby-5914-1a-versions.diff
>
>
> The list of compatible JRE versions is out of sync again. It currently says 1.4, 1.5, and 1.6.
> For trunk I believe we must remove 1.4, and we should add 1.7.
> For 10.9, if we want to change it, I think we can keep 1.4? And 1.7 was out and supported before we released 10.9, right?
> This issue was logged as DERBY-5078 the previous time it was out of sync.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira