Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (nike.apache.org: domain of craig.burlock@gmail.com
 designates 209.85.220.173 as permitted sender)
MIME-Version: 1.0
From: Craig Burlock <craig.burlock@gmail.com>
Date: Mon, 13 Aug 2012 10:09:41 +0930
Message-ID: 
 <CAJEb=WMctddc9Mbdxe6A4QZMD8Vy2Go0hrMpCrXDzjk5ndHC9Q@mail.gmail.com>
Subject: IVY Shared Repository version numbering without publish
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=20cf3079bf3a193e9604c71aefd6

--20cf3079bf3a193e9604c71aefd6
Content-Type: text/plain; charset=ISO-8859-1

Hello all,

I am currently trying to limit the growth of my IVY Cache by preventing the
major build products from being published (there is no reason to publish
them because no other build process needs to retrieve the final
applications).

Unfortunately my version numbers no longer increase because nothing is
being published for these jobs.

Is there a "nice" way to use IVY to increase version numbering for a
project that doesn't publish anything?

Should I just publish "something" (perhaps a ReadMe.txt file) in order to
force Ivy Shared Repository version folder creation, or is there a better
way?

--20cf3079bf3a193e9604c71aefd6--