From ivy-user-return-4214-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Tue Nov 11 13:13:30 2008 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 55427 invoked from network); 11 Nov 2008 13:13:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Nov 2008 13:13:30 -0000 Received: (qmail 3848 invoked by uid 500); 11 Nov 2008 13:13:37 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 3826 invoked by uid 500); 11 Nov 2008 13:13:36 -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 3815 invoked by uid 99); 11 Nov 2008 13:13:36 -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 05:13:36 -0800 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_HELO_PASS,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of nicolas.lalevee@hibnet.org does not designate 216.86.168.183 as permitted sender) Received: from [216.86.168.183] (HELO mxout-08.mxes.net) (216.86.168.183) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2008 13:12:17 +0000 Received: from [192.168.1.15] (unknown [79.80.26.73]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 848D6D05AD for ; Tue, 11 Nov 2008 08:12:57 -0500 (EST) Message-Id: <703F8FCD-05FB-4E01-A660-2DF85990E640@hibnet.org> From: =?ISO-8859-1?Q?Nicolas_Lalev=E9e?= To: ivy-user@ant.apache.org In-Reply-To: <8BF78BB6D10E854AAB3873A8A0B0679042B06CB9E1@LNWEXMBX0104.msad.ms.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v929.2) Subject: Re: Now Ivy RC2 is there a plan to add an IvyDE compatible version? Date: Tue, 11 Nov 2008 14:12:55 +0100 References: <8BF78BB6D10E854AAB3873A8A0B0679042B06CB997@LNWEXMBX0104.msad.ms.com> <46C8D22C-4924-4B70-B868-E3EC1744803A@hibnet.org> <8BF78BB6D10E854AAB3873A8A0B0679042B06CB9E1@LNWEXMBX0104.msad.ms.com> X-Mailer: Apple Mail (2.929.2) X-Virus-Checked: Checked by ClamAV on apache.org Le 11 nov. 08 =E0 09:44, Goldspink, Matt (IT) a =E9crit : > Hi Nicholas, > > Thanks for the reply. > >> Actually the new version of Ivy is already deployed in the IvyDE =20 >> updatesite, you can update it. > > It looks like Ivy RC2 is misspelt on the update site: > > id=3D"org.apache.ivy.feature" version=3D"2.0.0.cr2"> > > This caused an issue in Eclipse 3.4 because we'd had a previous =20 > version of ivy installed which was spelt correctly (i.e. 2.0.0.rc1) =20= > and now Eclipse seems to think 2.0.0.cr2 is older and won't update =20 > without an uninstall. I assume its doing basic ascii comparison and =20= > 'r' being greater than 'c' is causing it to fail. Actually this is not a mistake, because we want the final release be =20 called 2.0.0.final. So to keep the version ordered rc was called cr, =20 so 2.0.0.beta2 < 2.0.0.cr1 < 2.0.0.cr2 < 2.0.0.final. We fixed that version naming issue before the official release, but =20 you probably got a trunk build which still had rc1 in there. > > >> Note that the current implementation of the "resolve in workspace" >> feature is quite experimental, not very clean, but is a first step =20= >> towards a correct implementation. So use it with caution. > > My team (15 globally) have been using this feature across a =20 > workspace of 20 interdependent projects and so far, aside from =20 > patches we have submitted, we have not had any issues. If any =20 > changes are made to the implementation I'd be happy to test them out =20= > since they will probabbly have a big impact on our team. good to know. Thanks. Nicolas > > >> But yes it is time to think about an IvyDE release, I will start a =20= >> 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 =20= > 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 =20 > 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 =20 >> Workspace, >> in the past we've been taking a cut of the source code and using =20 >> that, >> but it would be nice if the official update site could provide us =20 >> 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 =20 > 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 =20 > discussion on the dev mailing list. > > Nicolas > -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. =20 > Sender does not intend to waive confidentiality or privilege. Use of =20= > this email is prohibited when received in error.