Hello,
This is a limitation, for which there's already an issue in JIRA:
https://issues.apache.org/jira/browse/IVY-528I suggest at least voting for it, or better submit a patch to fix it. The
problem is how repreport is implemented, it actually merely do a dependency
resolution. For this kind of things, I do think using a repository manager
would be better (instead of using a client side tool like Ivy). Note that
implementing specific solution with directory listing and xml parsing should
be pretty easy.
Xavier
On Mon, Jul 14, 2008 at 6:53 PM, <
Paul.Mackay@...> wrote:
> Hello,
>
> Any suggestions on this question?
>
> thanks
>
> paul
>
>
> >-----Original Message-----
> >From: ext
Paul.Mackay@... [mailto:
Paul.Mackay@...]
> >Sent: Monday, July 07, 2008 4:01 PM
> >To:
ivy-user@...
> >Subject: Organisation pattern not found using repreport
> >
> >Trying to use repreport I find that it cannot match any Ivy
> >files because the pattern used in the resolver does not
> >include [organisation]. However this was not a limitation in
> >other use cases.
> >Should repreport require that the pattern structure contains
> >[organisation]? Why not be able to find that information by
> >parsing the internals of the files?
> >
> >thanks
> >
> >paul
> >
> >
> >
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/http://ant.apache.org/ivy/http://www.xoocode.org/
