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: <318990263.1258396899778.JavaMail.jira@brutus>
Date: Mon, 16 Nov 2009 18:41:39 +0000 (UTC)
From: "Pierre-Arnaud Marcelot (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Resolved: (DIRSTUDIO-577) LDIF editor doesn't notify Eclipse
 that the LDIF file has changed when saving
In-Reply-To: <81250726.1257175259509.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-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre-Arnaud Marcelot resolved DIRSTUDIO-577.
----------------------------------------------

    Resolution: Fixed

Fixed in trunk at commit 880901.

http://svn.apache.org/viewvc?rev=880901&view=rev

> LDIF editor doesn't notify Eclipse that the LDIF file has changed when saving
> -----------------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-577
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-577
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldifeditor
>    Affects Versions: 1.4.0
>            Reporter: Aleksander Adamowski
>             Fix For: 1.5.1
>
>
> When saving a LDIF file after making modifications, Eclipse isn't properly notified that the file resource has changed.
> Because of that, several ill effects occur until the user manually refreshes (F5) the containing directory of any of ancestor directories:
> * the file doesn't appear in team synchronizing perspective if it had an unmodified status before being saved
> * search results involving the file aren't updated
> * the file doesn't appear in the list of files to be committed to version control system if it had an unmodified status before being saved
> * many other
> The LDIF editor should generate proper resource modified events.

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