ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mitch Gitman <>
Subject Re: I suspect I'm doing something I shouldn't
Date Tue, 18 Aug 2009 18:32:05 GMT
I think I found the answer to my particular problem. From the documentation
page on the deliver Ant
Deliver an ivy file without the private configurations:

<deliver conf="*(public)" />

I'd still be curious if there's ever a valid situation to publish a private
conf. In my situation though, I think the answer is no.

On Tue, Aug 18, 2009 at 8:19 AM, Mitch Gitman <> wrote:

> Maarten, I'm essentially resolving against an Ivy module that I expect was
> already published. And here's where I realize now that I'm doing something
> wrong, or at least strange. I'm publishing Ivy modules that have confs with
> visibility="private", but if they're already up on the Ivy repository,
> then those confs are never going to be reachable transitively through the
> module I'm immediately using.
> I'm doing the resolve programmatically and then checking the ResolveReport
> for unresolved dependencies:
>         IvyNode[] unresolvedDependencies =
> resolveReport.getUnresolvedDependencies();
> If I then call *IvyNode.getProblemMessage* on one of those unresolved
> nodes, I see that message about the conf being expected to be public.
> So now my question is, is there ever a valid situation where a published
> ivy.xml has a private conf? I'm making the distinction here between a
> published ivy.xml and the working ivy.xml for the current project.
> On Tue, Aug 18, 2009 at 1:08 AM, Maarten Coene <>wrote:
>> And could you also tell us how you resolve?
>> Maarten

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