Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 36101 invoked from network); 4 Dec 2006 22:07:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Dec 2006 22:07:56 -0000 Received: (qmail 854 invoked by uid 500); 4 Dec 2006 22:08:04 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 809 invoked by uid 500); 4 Dec 2006 22:08:04 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 793 invoked by uid 99); 4 Dec 2006 22:08:04 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 14:08:04 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of pajbam@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Dec 2006 14:07:53 -0800 Received: by ug-out-1314.google.com with SMTP id o2so2794722uge for ; Mon, 04 Dec 2006 14:07:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=cig4iCMxEY7MV/jyJkXkJr0jhIKBibQkzitxRz1upW3uL70B+qGNfSPFn4Lp5Eauj/uFZ5+/uyZnl3KuQTgl7ZdXl1W8qKzbynbMDZrw16L3ErbgPQ1kq5Nf57p7d8okPd/Tg8AqJr2rXbuuk7VQ8Fhk5xsbKoM/qifvfO1+uOo= Received: by 10.66.242.20 with SMTP id p20mr12742425ugh.1165270051958; Mon, 04 Dec 2006 14:07:31 -0800 (PST) Received: by 10.66.236.13 with HTTP; Mon, 4 Dec 2006 14:07:31 -0800 (PST) Message-ID: <98d8c0860612041407x18974933u631a33ccd6408a6b@mail.gmail.com> Date: Mon, 4 Dec 2006 23:07:31 +0100 From: "Pierre-Arnaud Marcelot" Sender: pajbam@gmail.com To: "Apache Directory Developers List" Subject: Re: In-Reply-To: <45749118.8050709@stefan-seelmann.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_54057_25613829.1165270051909" References: <11678555.1685351165226154087.JavaMail.servlet@kundenserver> <98d8c0860612040752s282d7243r925c2fe86f522491@mail.gmail.com> <45749118.8050709@stefan-seelmann.de> X-Google-Sender-Auth: 5d29c0bd7f6f3eb7 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_54057_25613829.1165270051909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Stefan, I will show if the shared-ldap LDIF utils could be used for the LDIF > editor. Does it makes sense to move the DSML parser to ldap-shared? Not yet I think. It still has major opened issues but as soon as it support binary values and those major issues are closed, its best place may be shared-ldap. There are some issues with big files in eclipse (see > > https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=big+large+files > ). > If we want to use the eclipse features (syntax coloring folding, content > assistence) this could be a real problem. The LDIF editor currently > rejects files bigger than 1MB. So, we may have exactly the same problem with a DSML Editor. It may even come sooner, since XML files are more verbose > I already tried to migrate to maven a few weeks ago and I got some > > issues regarding the internal Eclipse computed dependencies (that are > > necessary to build and run tests on plugins but should not be exported > > in the plugin itself since those dependencies will be supplied by the > > Eclipse platform or the RCP app). Have you ever successfully build an > > Eclipse plugin using Maven ? > No, not yet. > Ok, we'll work together on spare time to get LDAP Studio building with Maven. P-A ------=_Part_54057_25613829.1165270051909 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello Stefan,

I will show if the shared-ldap LDIF utils could be used for the LDIF
editor. Does it makes sense to move the DSML parser to ldap-shared?

Not yet I think. It still has major opened issues but as soon as it support binary values and those major issues are closed, its best place may be shared-ldap.

There are some issues with big files in eclipse (see
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=big+large+files).
If we want to use the eclipse features (syntax coloring folding, content
assistence) this could be a real problem. The LDIF editor currently
rejects files bigger than 1MB.

So, we may have exactly the same problem with a DSML Editor. It may even come sooner, since XML files are more verbose

> I already tried to migrate to maven a few weeks ago and I got some
> issues regarding the internal Eclipse computed dependencies (that are
> necessary to build and run tests on plugins but should not be exported
> in the plugin itself since those dependencies will be supplied by the
> Eclipse platform or the RCP app). Have you ever successfully build an
> Eclipse plugin using Maven ?
No, not yet.

Ok, we'll work together on spare time to get LDAP Studio building with Maven.

P-A
------=_Part_54057_25613829.1165270051909--