In addition to other uses of Ivy, we currently use Ivy's packager resolver with URL resources that exist externally on the Internet or are created locally by automated build procedures. In starting to learn about Artifactory, I had hoped to find that Artifactory could be used as a caching proxy for the resources that the packager resolver requires. Although Artifactory is able to cache a file whose URL is inconsistent with the expected layout for an external repository, I have run into at least two obstacles:
1. If the server where a file is hosted does not support HEAD requests, Artifactory will not try to retrieve the file. 2. URLs that do not directly specify the path of the requested file probably are not supported. Aside from the natural workaround of explicitly copying the problematic files to a local location (inside or outside artifactory), is there some other approach that might work for this scenario? Caching arbitrary URLs obviously is outside the domain for which Artifactory is intended. Is there a different tool that would be more appropriate for this need? -- View this message in context: http://forums.jfrog.org/Ivy-packager-resolver-tp7353683p7353683.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
