Re: [Artifactory-users] zip artifacts = resolving with maven

Hi Vano, This is not really an Artifactory limitation, but actually Maven is expecting to find a .pom file in order to resolve dependencies. If you are storing .zip files, you can specify 'zip' in your dependency declaration to tell maven that the artifact you wish to resolve is a zip file and

Re: [Artifactory-users] Create Empty Folder

Hi Raj, You can use this REST api to create an empty folder in Artifactory. Regards, Itamar -- View this message in context:

Re: [Artifactory-users] Artifactory Pro Vagrant repo and box update

Okay, I've solved this myself. Turns out there is a bug in the version of Vagrant I was using that was not passing the ATLAS_TOKEN to Artifactory when requesting the BOX. I was using Vagrant 1.8.1, the issue is supposedly fixed in 1.8.3, and I've installed the latest 1.8.5, which seems to also

[Artifactory-users] Artifactory Pro Vagrant repo and box update

We recently setup an AP installation and created an Vagrant repo. I've been able to successfully deploy boxes to Artifactory as well as downloading new boxes from Artificatory via vagrant box add https://myartifactory But what I cannot get to work is `vagrant box update`, I just get a 401

[Artifactory-users] VSTS plugin running on Linux

The current Artifactory VSTS Plugin described at https://www.jfrog.com/confluence/display/RTF/VS+Team+Services+Artifactory+Plugin is implemented as as PowerShell script, so it would not run on Linux build/deploy agent. Is there any plan to implement the plugin in a cross-platform manner with Node

Re: [Artifactory-users] VSTS plugin running on Linux

The portion of the plugin that is PowerShell is probably the piece that goes onto the VSTS server, which is Windows only AFAIK. The plugin that you install in Artifactory should be Java/Groovy, because that is what Artifactory itself is programmed in. If you have a Linux VSTS build agent you can

Re: [Artifactory-users] VSTS plugin running on Linux

Thank you for your answer Ethan, It does appear that the task is actually running on the build agent. Here is the error: 2016-07-29T01:36:52.8159870Z ##[section]Starting: JFrogArtifactoryPromote 2016-07-29T01:36:53.0988410Z ##[error]Supported task execution handler not found. Supported handlers: