Hi,
For HTTP-based repositories it looks like Ivy is doing HTML pattern-matching
to figure out the available versions. This is done by requesting the path of
the group, then Ivy is looking for suitable href tags in the markup of the
response.
We have tried (programmaticaly) to get the list of versions with both Ivy
2.0.0 and 2.1.0-rc2, and found out it does indeed break in 2.0.0, but works
fine in 2.1.0-rc2 (tested with the trunk of Artifactory 2.1.0, but I expect
the behavior to be the same with 2.0.8). This is probably related to
http://issues.apache.org/jira/browse/IVY-959.
So, if you are using Ivy 2.0.0, we expect Ivy 2.1.0-rc1 and above to be able
to successfully resolve dynamic versions with Artifactory.
Hope it helps,
Yoav
On Fri, Sep 11, 2009 at 7:08 AM, cquinn <[email protected]> wrote:
>
> I am having trouble similar to what topher1120 describes in his Aug 10,
> 2009
> post, but maybe even more fundamental.
>
> I am having a hard time getting Ivy to resolve artifacts in Artifactory
> when
> the dependency spec uses wildcards or ranges in the revision (version).
> When
> the revisions are concrete, resolution works fine, but when they are not,
> the artifacts are just not found.
>
> I have a bunch of 3rd party artifacts in the repository with corresponding
> Ivy files. Like:
>
>
> commons-collections/commons-collections/2.1.1/commons-collections-2.1.1.jar
> commons-collections/commons-collections/2.1.1/ivy-2.1.1.xml
>
> commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar
> commons-collections/commons-collections/3.2.1/ivy-3.2.1.xml
>
> I have tried both ibiblio and url resolvers, with pretty much every
> combination of flags.
>
> I guess I don't quite have a complete understanding of how this is supposed
> to work. That is, how can Ivy query/enumerate the available versions of the
> module using a URL?
>
> When I throw these artifacts and module descriptors onto the disk and use a
> filesystem resolver, it works fine.
>
> Any ideas? Suggestions for good reading would be appreciated too. It's hard
> to find good info on Ivy + Artifactory together.
> --
> View this message in context:
> http://www.nabble.com/Ivy-resolving-wildcard-revisions-w--Artifactory-tp25394756p25394756.html
> Sent from the Artifactory-Users mailing list archive at Nabble.com.
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
