I had considered something along those lines, but as you said it gets tricky
and I thought there would have to be a better way.
I find managing promotions through Artifactory especially appealing because
we can then ensure only those users with the correct role can actually do
the promotion, but we really don't want to be forced to rebuild the
application just to change the Ivy status of the artifacts from
"integration" to "release."
Would this be a reasonable feature request of Artifactory?
Anyone else? Should I expand my question to the Ivy users mailing list?
Surely I'm not the first one to bump into this?
Thanks,
Rich
On Fri, Feb 19, 2010 at 11:09 AM, Carlton Brown <[email protected]>wrote:
> Not specific to Artifactory, but I used to implement this pattern with a
> hack like this:
>
> 1) ivy:install artifact to a local temp repository
> 2) ivy:deliver the ivy.xml with new metadata tokens
> 3) ivy:publish into the destination repository
>
> It's a little tricky because you have to mix the semantics of a repository
> with the semantics of a workspace. You're installing to it, manipulating
> the data, and then publishing from it.
>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
