Sorry. I did not follow this the last days. Anyway Maarten explained correctly what I wanted to say. M.
2011/1/6 Mitch Gitman <mgit...@gmail.com> > Thanks to Maarten. Apologies to Martin. I did misinterpret Martin's answer > after all. Yes, this is a critical feature. Certainly when you're > prolifically versioning CI builds (whether with a timestamp or > buildnumber), > you should be replacing dynamic revisions. And no, I don't recall off the > top of my head how to do the same with Maven. > > Maarten, I should at least be able to share a video. Not sure about the > slides themselves because of copyright issues, and they probably won't > stand > on their own anyway since I'll be trying out a "presentation zen" approach. > > Anyway, keep 'em coming, folks. My great fear with a talk like this is > failing to communicate one of the most compelling use cases or features. > > On Wed, Jan 5, 2011 at 3:22 PM, Maarten Coene <maarten_co...@yahoo.com > >wrote: > > > Mitch, > > > > first of all, this seems a very interesting presentation topic. Is there > > any > > chance you could share this presentation with us? > > > > secondly, I think what Martin meant was this: > > > > suppose your ivy.xml file contains a dynamic dependency declaration like: > > <dependency org="org.apache" name="foo" rev="[1.0, 2.0[" /> > > > > If you publish this ivy.xml file to a repository, you can tell Ivy to > > replace > > the dynamic revision with a static one. > > So when at the time of publishing, the version of foo in the repository > was > > "1.8", the published ivy.xml will look like: > > <dependency org="org.apache" name="foo" rev="1.8" /> > > > > Maarten > > > > > > >
