Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 44928 invoked from network); 11 Nov 2008 08:46:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Nov 2008 08:46:03 -0000 Received: (qmail 824 invoked by uid 500); 11 Nov 2008 08:46:09 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 789 invoked by uid 500); 11 Nov 2008 08:46:09 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 778 invoked by uid 99); 11 Nov 2008 08:46:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2008 00:46:09 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Matthew.Goldspink@morganstanley.com designates 205.228.53.69 as permitted sender) Received: from [205.228.53.69] (HELO hqmtaint02.ms.com) (205.228.53.69) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2008 08:44:49 +0000 Received: from hqmtaint02 (localhost.ms.com [127.0.0.1]) by hqmtaint02.ms.com (output Postfix) with ESMTP id A09D8E38AA7 for ; Tue, 11 Nov 2008 03:45:01 -0500 (EST) Received: from ny0030as02 (unknown [170.74.93.68]) by hqmtaint02.ms.com (internal Postfix) with ESMTP id 7C52E110032 for ; Tue, 11 Nov 2008 03:45:01 -0500 (EST) Received: from ny0030as02 (localhost [127.0.0.1]) by ny0030as02 (msa-out Postfix) with ESMTP id 6413DAB80B4 for ; Tue, 11 Nov 2008 03:45:01 -0500 (EST) Received: from PIWEXOB01.msad.ms.com (piwexob01 [144.14.3.72]) by ny0030as02 (mta-in Postfix) with ESMTP id 61A975CC02F for ; Tue, 11 Nov 2008 03:45:01 -0500 (EST) Received: from PAEXCAT01.msad.ms.com ([10.163.18.210]) by PIWEXOB01.msad.ms.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 11 Nov 2008 03:45:01 -0500 Received: from OYWEXHUB02.msad.ms.com (10.174.169.82) by PAEXCAT01.msad.ms.com (10.163.18.210) with Microsoft SMTP Server (TLS) id 8.1.291.1; Tue, 11 Nov 2008 03:45:00 -0500 Received: from LNWEXMBX0104.msad.ms.com ([10.174.156.26]) by OYWEXHUB02.msad.ms.com ([10.174.169.82]) with mapi; Tue, 11 Nov 2008 08:45:00 +0000 From: "Goldspink, Matt \(IT\)" To: Date: Tue, 11 Nov 2008 08:44:59 +0000 Subject: RE: Now Ivy RC2 is there a plan to add an IvyDE compatible version? Thread-Topic: Now Ivy RC2 is there a plan to add an IvyDE compatible version? Thread-Index: AclDfh4/DrVsiLINToi33Sz6GuQdYAAWIbsQ Message-ID: <8BF78BB6D10E854AAB3873A8A0B0679042B06CB9E1@LNWEXMBX0104.msad.ms.com> References: <8BF78BB6D10E854AAB3873A8A0B0679042B06CB997@LNWEXMBX0104.msad.ms.com> <46C8D22C-4924-4B70-B868-E3EC1744803A@hibnet.org> In-Reply-To: <46C8D22C-4924-4B70-B868-E3EC1744803A@hibnet.org> Content-class: urn:content-classes:message Accept-Language: en-US x-mimeole: Produced By Microsoft MimeOLE V6.00.3790.3168 Content-Language: en-US Importance: normal Priority: normal X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginalArrivalTime: 11 Nov 2008 08:45:01.0193 (UTC) FILETIME=[C8C29790:01C943D9] X-Anti-Virus: Kaspersky Anti-Virus for MailServers 5.5.35/RELEASE, bases: 11112008 #1237191, status: clean X-Virus-Checked: Checked by ClamAV on apache.org Hi Nicholas, Thanks for the reply. > Actually the new version of Ivy is already deployed in the IvyDE = updatesite, you can update it. It looks like Ivy RC2 is misspelt on the update site: This caused an issue in Eclipse 3.4 because we'd had a previous version = of ivy installed which was spelt correctly (i.e. 2.0.0.rc1) and now = Eclipse seems to think 2.0.0.cr2 is older and won't update without an = uninstall. I assume its doing basic ascii comparison and 'r' being = greater than 'c' is causing it to fail. > Note that the current implementation of the "resolve in workspace" > feature is quite experimental, not very clean, but is a first step = towards a correct implementation. So use it with caution. My team (15 globally) have been using this feature across a workspace of = 20 interdependent projects and so far, aside from patches we have = submitted, we have not had any issues. If any changes are made to the = implementation I'd be happy to test them out since they will probabbly = have a big impact on our team. > But yes it is time to think about an IvyDE release, I will start a = discussion on the dev mailing list. Great! I'll keep an eye out for any updates. Thanks, Matt -----Original Message----- From: Nicolas Lalev=E9e [mailto:nicolas.lalevee@hibnet.org] Sent: 10 November 2008 21:47 To: ivy-user@ant.apache.org Subject: Re: Now Ivy RC2 is there a plan to add an IvyDE compatible = version? Le 10 nov. 08 =E0 18:01, Goldspink, Matt (IT) a =E9crit : > Hi, > > Now that Ivy RC2 is out is it possible to get an IvyDE compatible > version added to the IvyDE update site? Actually the new version of Ivy is already deployed in the IvyDE = updatesite, you can update it. The current released version of IvyDE (2.0.0.alpha1) is compatible with it. > We'd like to use some of the new features like Resolving in Workspace, > in the past we've been taking a cut of the source code and using that, > but it would be nice if the official update site could provide us with > a compatible version. Note that the current implementation of the "resolve in workspace" feature is quite experimental, not very clean, but is a first step = towards a correct implementation. So use it with caution. > Is there any date we can expect one by? No date scheduled by now. But yes it is time to think about an IvyDE release, I will start a = discussion on the dev mailing list. Nicolas -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender = does not intend to waive confidentiality or privilege. Use of this email = is prohibited when received in error.