ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave <davidcor...@gmail.com>
Subject Ivy Status usage question
Date Fri, 13 Jun 2008 14:06:53 GMT
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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message