On 09/19/2014 06:07 PM, Taylor Braun-Jones wrote:
On Fri, Sep 19, 2014 at 3:04 PM, Brad King wrote:
I think it can be activated by a special format of an entry in
ExternalData_URL_TEMPLATES that specifies a lookup key that maps
to some kind of custom configuration of a .cmake script to include
On Mon, Sep 22, 2014 at 10:07 AM, Brad King brad.k...@kitware.com wrote:
Perhaps:
list(APPEND ExternalData_URL_TEMPLATES
ExternalDataCustomScript://MyFetch/%(algo)/%(hash)
)
set(ExternalData_CUSTOM_SCRIPT_MyFetch /path/to/MyFetch.cmake)
The script would be include()-ed in
Shifting discussion to cmake-developers.
On Fri, Sep 19, 2014 at 3:04 PM, Brad King brad.k...@kitware.com wrote:
On 09/19/2014 12:23 PM, Taylor Braun-Jones wrote:
integrate Artifactory with the ExternalData framework?
the Artifactory REST API is a two step process
I think it can be
Hi all,
I'm curious if anyone has attempted to integrate Artifactory with the
ExternalData framework?
Unfortunately the Artifactory REST API is a two step process where you
first search for a file based on MD5 or SHA1 hash[1] which returns JSON
results the file's URI. You then issue a second
On 09/19/2014 12:23 PM, Taylor Braun-Jones wrote:
integrate Artifactory with the ExternalData framework?
the Artifactory REST API is a two step process
Currently ExternalData always uses the file(DOWNLOAD) command.
Recently I was thinking about how to extend the ExternalData
module to support
