Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <423688810.1128016490340.JavaMail.jira@ajax.apache.org>
Date: Thu, 29 Sep 2005 19:54:50 +0200 (CEST)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Reopened: (DERBY-476) Derby UI plug-in version 1.0.0
 incompatible with Eclipse 3.1 M6 or higher
In-Reply-To: <1790240405.1122511818845.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-476?page=all ]
     
Deepa Remesh reopened DERBY-476:
--------------------------------


reopening to fix fix version

> Derby UI plug-in version 1.0.0 incompatible with Eclipse 3.1 M6 or higher
> -------------------------------------------------------------------------
>
>          Key: DERBY-476
>          URL: http://issues.apache.org/jira/browse/DERBY-476
>      Project: Derby
>         Type: Bug
>   Components: Tools
>     Reporter: Susan Cline
>     Assignee: Susan Cline
>      Fix For: 10.1.1.0, 10.1.2.0, 10.2.0.0, 10.1.1.1
>  Attachments: launch_patch.diff
>
> Per this email thread:
> http://mail-archives.apache.org/mod_mbox/db-derby-user/200506.mbox/%3c20050606165347.40256.qmail@web81302.mail.yahoo.com%3e
> The Derby UI plugin throws an exception when trying to start the Derby network server with Eclipse 3.1M6 or higher.
> The fix for this is simple, and involves only changing a class name in 4 files per the email above.  Eclipse 3.1 is now GA so this fix should be made to the UI plug-in which will allow it to work with the current release of Eclipse.  
> Also, by adding this fix the plug-ins will no longer work with 3.0.x through 3.1M5 builds of Eclipse.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira