From ivy-user-return-3365-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Fri Jun 13 14:07:23 2008 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 11807 invoked from network); 13 Jun 2008 14:07:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jun 2008 14:07:22 -0000 Received: (qmail 34411 invoked by uid 500); 13 Jun 2008 14:07:24 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 34394 invoked by uid 500); 13 Jun 2008 14:07:24 -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 34383 invoked by uid 99); 13 Jun 2008 14:07:24 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2008 07:07:24 -0700 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 (athena.apache.org: domain of davidcorley@gmail.com designates 209.85.198.244 as permitted sender) Received: from [209.85.198.244] (HELO rv-out-0708.google.com) (209.85.198.244) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2008 14:06:35 +0000 Received: by rv-out-0708.google.com with SMTP id b17so3852654rvf.40 for ; Fri, 13 Jun 2008 07:06:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=WIRhWox1sPEW1248ptBu/OZmpLMbe8Axc3IUmaHxRFU=; b=tHStuBVJW8cwDyUk2rIvR+AbhIaI2Nbw4YWp69wNfQMh0KaL+4ntX8+ePQuxwCou4V 2ZvU7RAniXzME72iyAKpuOtkxL+4/wOFjaT3Y+JcPpBRTH/p6cPgFpXnEjvlXGhrSFXC J51qBa6fOk/LA8vszvaFZoomzAaRuxs0TnVmo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=DcyMa+AtNR5qaa1L/qdYFPjl6j39xT0a316tNrgtWxYKzFmgx9qxgaK4JXkQkz5Vo7 rAJptG3Y7j1H4dMoBy/MHg0c1nhYb5qdcFVxCH72PV+tpvdS961mjBuOYkLM6tpe474N 4utPOBMbLfrWyA0MCEjEAIg2E9DLyatEUTvxs= Received: by 10.141.22.1 with SMTP id z1mr1844735rvi.67.1213366013735; Fri, 13 Jun 2008 07:06:53 -0700 (PDT) Received: by 10.140.255.16 with HTTP; Fri, 13 Jun 2008 07:06:53 -0700 (PDT) Message-ID: <26c776bf0806130706v2e29e353ra4b77fc83622b1c7@mail.gmail.com> Date: Fri, 13 Jun 2008 15:06:53 +0100 From: Dave To: ivy-user@ant.apache.org Subject: Ivy Status usage question MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10658_25825116.1213366013743" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_10658_25825116.1213366013743 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hey all, I'm still coming to grips with the power of Ivy (it's a really extraordinary tool), and I've a question I'm hoping you can help me with. I have a component called "common". I'd like to be able to store 3 versions in our shared repository. 1. A released version 1.0 2. A development version so other components can get the latest changes quickly 3. An integration testing version, which is a milestone of the development version. I intend to map the following existing Ivy status to each version 1 = Release 2 = Integration 3 = Milestone 2 and 3 will eventually become release 1.1 I'd like to know what's the best way of handling such a situation so that it's as little maintenance as possible. Should I use a repository with: common/1.0 common/1.1dev common/1.1integ or should I just have a common folder without any version sub-folders, and create versioned jars and ivy files for each artifact publishing them all the same common folder? Any best practice tips for me in this regard? Thanks in advance, Dave -- There are 10 types of people in the world. Those who understand binary and those who do not. ------=_Part_10658_25825116.1213366013743--