Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 76232 invoked from network); 27 Dec 2007 18:01:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Dec 2007 18:01:04 -0000 Received: (qmail 19194 invoked by uid 500); 27 Dec 2007 18:00:53 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 19144 invoked by uid 500); 27 Dec 2007 18:00:52 -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 19133 invoked by uid 99); 27 Dec 2007 18:00:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Dec 2007 10:00:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NORMAL_HTTP_TO_IP,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elecharny@gmail.com designates 209.85.128.184 as permitted sender) Received: from [209.85.128.184] (HELO fk-out-0910.google.com) (209.85.128.184) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Dec 2007 18:00:28 +0000 Received: by fk-out-0910.google.com with SMTP id z22so4271437fkz.9 for ; Thu, 27 Dec 2007 10:00:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=bQtIbWX+KfZR/XQbzj/hscUkclPaFlzH3dGsb9ZTx/g=; b=ZB65vShoR5MvvL9LR8/J1tmP8lfMWC4apmVPhf6KfJ953rptNaNvee+HZdpVTPCC0/FrEDUZo+1fo/qwVI3aVqsv8Ebi8ZsScPr0HD+s0newkJushMJWNK1USoP1y+g5EPwStot+06tfhfT/6m4rwIs6MC+OtJPma422zNyFAjQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=eF/3d5KiUgqmPj+WiSrXZWA5+dMtWtZ0EfyJc4RZYttrrce3FjjZHwFpF1QRjLe0SbGIHxbd9xtZgCSUiErO4vTAK2W4H41eVUvWHR5/0FjUe/CtaLU8qdUJJKSkPuv2x9cpdVbq5vhel1HSJpBG1063uK2NDG4bt4INi5tzjZ4= Received: by 10.82.174.20 with SMTP id w20mr14953906bue.28.1198778431194; Thu, 27 Dec 2007 10:00:31 -0800 (PST) Received: from ?192.168.1.5? ( [82.245.116.110]) by mx.google.com with ESMTPS id w5sm24232956mue.2.2007.12.27.10.00.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 Dec 2007 10:00:30 -0800 (PST) Message-ID: <4773E815.3090803@gmail.com> Date: Thu, 27 Dec 2007 18:59:49 +0100 From: Emmanuel Lecharny User-Agent: Thunderbird 1.5.0.14pre (X11/20071023) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [Studio] Eclipse 3.3.1 dependencies + "Mavenization" of the trunk References: <98d8c0860712270952v5f2651d7ld35dd40a1497d5d4@mail.gmail.com> In-Reply-To: <98d8c0860712270952v5f2651d7ld35dd40a1497d5d4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Pierre-Arnaud Marcelot wrote: > Hi all, > > I'm happy to tell you that I have successfully generated new launchers > (for each platform we support - Mac OS X, Linux and Windows) using > Eclipse 3.3.1 dependencies (the latest 3.3.1.1 to be > precise). Just great !!! > > They can be tested on this branch : > https://svn.apache.org/repos/asf/directory/studio/branches/studio-eclipse-3.3 > > > I think that moving from the old 3.2 to the latest 3.3.1.1 > Eclipse dependencies could be another great feature > for Apache Directory Studio 1.1.0. This update has fixed bugs in the > core of Eclipse (and has significantly improved the way widgets are > drawn on Mac OS X - at last...). > > I was wondering if everybody was OK with releasing Studio 1.1.0 with > Eclipse 3.3 dependencies. WDYT ? +1 for me. > > > I also had a talk with Emmanuel about the "mavenization" of the trunk > before releasing Studio 1.1.0. > Stefan Seelmann and I were more thinking of switching from Ant+Ivy to > Maven after the release, but it could also be interesting to delay a > little bit the release and use this time to switch our build system. > This would help us a lot for future releases, especially if we need to > release a 1.1.1 soon after 1.1.0. > > Do you think we should "Mavenize" the build before releasing Studio > 1.1.0 ? We are not in a hurry, I think. We can wait a bit to get maven in the loop : otherwise, we will have to wait a long time before having maven for studio. And also, I think that we need to leverage Felix work, because it's ok to work in a sandbox, but at some point, going for real is much better :) > > Thanks in advance for your wise answers, > Pierre-Arnaud Marcelot Thanks for your great work ! -- -- cordialement, regards, Emmanuel L�charny www.iktek.com directory.apache.org