Just found another solution.... instead of "useOrigin" on the "publish"
task, set "changing=true" on the dependency in ivy.xml. That seems to work
without any deprecation warnings. It also seems to update the cache, which
seems more proper.
On Tue, Jan 24, 2012 at 9:52 AM, John Sokel <jso...@grubhub.com> wrote:
> "forcedeliver" did not in itself solve the problem, the dependent project
> still put the artifact in the cache and then that was still used. I did
> however try using the "useOrigin" setting on "resolve", which seems to
> prevent the jar from going to the cache. This seems like a viable
> solution except that when running, the output says:
>
> DEPRECATED: useOrigin option is deprecated when calling resolve, use
> useOrigin setting on the cache implementation instead
>
> I never created my own cache settings (just used the default). So, I am
> going to go with this for now, and play with cache settings later.
>
> Thanks for the help.
>
>
> On Tue, Jan 24, 2012 at 12:49 AM, Xavier MARTIN <zeflas...@gmail.com>wrote:
>
>> A quick answer from my cellphone.
>> Try to check the forcedeliver option or try to use the last strategy using
>> a custom logic for it... Ivy doc talks about this.
>>
>> + +
>> On Jan 24, 2012 5:42 AM, "Not Zippy" <notzi...@gmail.com> wrote:
>>
>> > I have 6 projects dependent on each other. I setup the dependency in
>> ivy
>> > based on a property so I can change them dynamicly like
>> > <dependency conf="hidden->hidden" org="foo" name="project.a"
>> > rev="${project.a.rev}"/>
>> >
>> > then the property is specified elsewhere (in the ant script or eclipse)
>> > like project.a.rev=latest.integration
>> > "latest.integration" means always use the latest builds local or remote
>> >
>> > So if I want to change this dependency to a particular release all I
>> need
>> > to do is change the property
>> > project.a.rev=qa-release-1.*
>> > (Note the wild card allows the revision to be unspecific)
>> >
>> >
>> > Does that help ?
>> > NZ
>> >
>> >
>> > On Mon, Jan 23, 2012 at 8:30 AM, John Sokel <jso...@grubhub.com> wrote:
>> >
>> > > I have spent the entire weekend trying to make ivy work for me and ivy
>> > > seems to be fundamentally opposed to what I want to do. A quick
>> > > background:
>> > >
>> > > - I have 5 different projects, with a varying level of dependencies
>> (A,B
>> > > dep on C; B,C dep on D, all dep on E).
>> > > - I have 3 different builds going with our CI server: trunk, QA
>> branch,
>> > > PROD branch
>> > > - At any time a developer can run one of these 3 active branches (or
>> all
>> > > three)
>> > > - I want to publish each artifact with up to 3 versions: trunk, qa,
>> prod.
>> > > No number scheme desired.
>> > > Example: A-trunk.jar A-qa.jar A-prod.jar, B-trunk.jar B-qa.jar
>> > > B-prod.jar, etc.
>> > > - I want the dependent projects to get the last built artifact that
>> was
>> > > published.
>>
>
--
*happy eating
John Sokel* | jso...@grubhub.com
GrubHub | Director of Technology
p 773-391-9566
2211 N Elston, 4th Floor
Chicago, IL 60614
