ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart" <>
Subject RE: tagging
Date Thu, 21 Jun 2007 12:16:50 GMT
What I would do implement such a use case is to use different repository.
I would put a QA repository, a staging repository and a release repository.

When you want to promote a release you can use ivy install task to copy
dependency from one repository to an other.

I would prefer this approach because I don't like the idea of changing a
repository. Changing/versioning meta-data is something that has already been
discussed and will certainly come back again.  But for the moment we don't
have nice solution for that.

Now, it is also possible that we miss some features to support build
promotions from one repository to an other.  (I think to meta-data
transformation, dependency checks, or something else).

If you feel such features are missing, don't hesitate to raise a jira
feature request.


> -----Original Message-----
> From: testn []
> Sent: jeudi 21 juin 2007 13:13
> To:
> Subject: tagging
> Hi,
> I think I can see another use case of ivy as follows:
> 1. You build a library and publish it as QA release.
> 2. Once you deploy the application and QA people test it and it is ok
> 3. You would want to tag the same jar as STAGE tag
> 4. When you want to deploy the same jar to STAGE environment, you would
> need
> to get the STAGE version
> 5. and you would do the same thing for production version.
> I would like to know whether there is any mechanism in place to do
> something
> like this... Do you think "latest.integration" is already good enough for
> this? I just think this use case is not like "branch" or "release" since
> you
> can have multiple tags on the same version and the tag can move along the
> version as time goes by.
> --
> View this message in context:
> tf3958045.html#a11230965
> Sent from the ivy-user mailing list archive at

View raw message