Awesome.   Great news.  I’ll try it out.

 

From: Yoav Landman [mailto:[email protected]] 
Sent: Wednesday, December 02, 2009 4:46 PM
To: [email protected]
Subject: Re: [Artifactory-users] Ivy dynamic revisions don't 
resolvethroughArtifactory

 

There are in Artifactory :) 

You can see them if you select a version folder in the tree browser and then 
select the metadata tab.

With the ibibilio resolver Ivy would send requests for this data when resolving 
versions.

On Wed, Dec 2, 2009 at 11:40 PM, Carlton Brown <[email protected]> wrote:

Thanks for the response… I could be missing something, but in an Ivy repository 
there wouldn’t be any maven-metadata.xml file would there?    

 

From: Yoav Landman [mailto:[email protected]] 
Sent: Wednesday, December 02, 2009 4:37 PM
To: [email protected]
Subject: Re: [Artifactory-users] Ivy dynamic revisions don't resolve 
throughArtifactory

 

What you should do is point to a virtual repository url, not a remote one, e.g. 
http://server:8081/artifactory/repo, and make sure to use Ivy 2.1, since IIRC 
2.0 had some bugs with href parsing.

An even better approach would be to use the ibiblio resolver - it doesn't rely 
on HTML parsing to extract versions but instead uses the more strict 
maven-metadata.xml format.

On Wed, Dec 2, 2009 at 6:38 PM, Carlton Brown <[email protected]> wrote:

Thought I’d try this again, reworded and under a different subject.

 

One of the core features of Ivy is dynamic version resolution.   For example, I 
can request an artifact using a version number like ‘1.0.+’ or 
‘latest.integration’.    Ivy performs a directory listing of the URL to see 
what is available, and retrieves the appropriate version.

 

This doesn’t work with Artifactory.   The problem seems to be that it does not 
return a consistent directory listing.   For example:

 

If I try to access a URL like:

http:// myhost/artifactory/myrepo/group/module

 

I get an HTML document with HREF’s to pages like:

http:// myhost/artifactory/myrepo-cache/group/module/version

 

If the hrefs URL’s pointed to ‘myrepo’ instead of ‘myrepo-cache’ then Ivy could 
resolve the versions.   But as it is, Ivy can’t resolve dynamically.

 

I’m new to Artifactory and I can’t seem to find any way to set this up (or 
something like it, via WebDAV).   I opened an Ivy issue and they basically sent 
me back to you guys.  https://issues.apache.org/jira/browse/IVY-1140

 

Again, dynamic version resolution in this manner is a foundational feature of 
Ivy.   I really like Artifactory and want to use it with Ivy, but if 
Artifactory can’t support directory listing & dynamic version resolution, then 
it really doesn’t support Ivy in any meaningful sense.   Not trying to be 
provocative with this comment, just trying to state the situation plainly.   
Apologies if I have missed some newbie mistake or overlooked part of the doc.

 

Thanks,

Carlton 

***CONFIDENTIALITY NOTICE and DISCLAIMER*** 
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
 
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.


------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

 

***CONFIDENTIALITY NOTICE and DISCLAIMER*** 
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.


------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

 


***CONFIDENTIALITY NOTICE and DISCLAIMER*** 
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure and solely for
the use of the person(s) or entity to whom it is intended. If you
have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this
message and any attachment from your system. If you are not the
intended recipient, be advised that any use of this message is
prohibited and may be unlawful, and you must not copy this
message or attachment or disclose the contents to any other person.
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to