Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <18164008.1181931806621.JavaMail.jira@brutus>
Date: Fri, 15 Jun 2007 11:23:26 -0700 (PDT)
From: "Frank Krasicki (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Commented: (DIRSTUDIO-137) Eclipse 3.2 and LDap Studio
 schema creation cause flaky behavior of Eclipse.  Wallpaper and random
 frame corruption ensue.
In-Reply-To: <28383076.1181660487883.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DIRSTUDIO-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505337 ] 

Frank Krasicki commented on DIRSTUDIO-137:
------------------------------------------

>From every indication within eclipse I had thought I had changed to Java 1.5
.

I removed 1.6 from the machine and then once again scrubbed Eclipse
preferences, this time finding an instance of a runtime setting set to 1.6.

I changed that to 1.5 and retried LDapStudio and so far it is working like a
charm.

Thanks for the goodwill.  i had not noticed the discrepency primary because
I thought I had already made that correction.

cheers,

Frank Krasicki


> Eclipse 3.2 and LDap Studio schema creation cause flaky behavior of Eclipse.  Wallpaper and random frame corruption ensue.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-137
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-137
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-schemas
>    Affects Versions: 0.8.0
>         Environment: Eclipse 3.2, XP on a dual boot  development box.  0.8.0 schema editor plug-in, ApacheDS 1.5.0
>            Reporter: Frank Krasicki
>
> Creating a new schema file works fine.  Attempting to create a schema object corrupts all processing.  Eclipse can hang or create disruptive behaviors.  File cannot be saved thereafter. Behavior can affect desktop access as well.

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