On Sun, Sep 13, 2009 at 12:40 AM, Carl Quinn <[email protected]> wrote:
>
> I am using Ivy 2.1.0-rc2 with Artifactory 2.0.7. Do you think Artifactory
> 2.0.8 would be any different? Or should I even try out the 2.1.0 trunk?
>
I guess my first question should have been what Artifactory version you are
using :)
>
> Also, what Ivy resolvers & settings did you find successful with your
> programatic tests?
>
We tested programatically resolving the correct list of versions (assuming
that when this work the Ivy client will take care of the rest). We used the
URL resolver in m2-compatible mode and default Ivy settings. We tried both
virtual repo URLs and local repo URLs as the repo root.
We already tested both 2.0.7 and 2.0.8 with the same test case and it worked
fine.
>
> I am a little surprised that there isn't a more rest-full (non-html) way
> for
> Ivy to talk to the repository.
>
Actually, the ibiblio resolver uses the maven-metadata.xml by default to get
the list of versions, which can be seen as a more restful way.
>
> --carl
>
>
Since getting the list of versions worked fine in all our tests, we assumed
that once Ivy is getting back a correct list of versions from the repository
something else goes wrong, so we also ran a full standalone Ivy test, with
the following settings:
<ivysettings>
<settings defaultResolver="url"/>
<resolvers>
<url name="url" m2compatible="true">
<artifact
pattern="${test.repoRoot}/[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"
/>
</url>
</resolvers>
</ivysettings>
We used test.repoRoot = http://server:8081/artifactory/repo
And ran something like:
java -jar ivy.jar -settings <the-above-ivysettings-file> -dependency mysql
connector-java [5.1.0,5.2.0]
And that also worked as expected, resolving the correct artifact version.
Do you have a particular version pattern that fails for you that we can try
out?
Yoav
>
> Yoav Landman-3 wrote:
> >
> > 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
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Ivy-resolving-wildcard-revisions-w--Artifactory-tp25394756p25418461.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
