Artifactory moved to support APIKEY only. If your old _auth was base64 encoding of username:password or username:encrypted_password then both are unacceptable now. You must use APIKEY in place of these. So, the supported _auth now becomes: _auth: APIKEY But ironically, even this didn’t work in some cases. Following seemed to be more reliable: You need … Read more
Two thoughts come to mind: The path structure in your internal repository for your artifact is incorrect. I suggest running the maven command with -X parameter. It will display the maven’s attempt at downloading the files. Get the line that has your repository as the url and try and look for it yourself. The path … Read more
Both Artifactory and Nexus can handle any type of file, as they both are “Binary Repository Managers”. Albeit that, Nexus can technically store any file, but lacks support for binaries that do not adhere to the Maven repository layout. For example, such files will not be indexed and cannot be retrieved in searches; Also, if … Read more
You can use the Maven Dependency Plugin goal get together with LATEST as version for your artifact: mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:get -DremoteRepositories=<URL_to_your_maven_repo> -Dartifact=<group_id>:<artifact_id>:LATEST -Dpackaging=jar -Ddest=<target_dir>/<artifact_name>.jar
I think the root of your problem is likely caching. NPM caches packages that have been downloaded, so they don’t have to be downloaded again, and they can even be re-installed offline if necessary. It also caches the resolved value for later use. If a package of the same version has already been resolved and … Read more
The problem was that when I added the various bits to the sibling project that meant I had two projects defining the buildscript {} section. buildscript { … dependencies { classpath group:’org.jfrog.buildinfo’, name: ‘build-info-extractor-gradle’, version: ‘3.0.1’ } } Apparently that caused two different versions of the dependency to exist in the classpath, hence the error. … Read more
curl POST did not work for me . PUT worked correctly . The usage is curl -X PUT $SERVER/$PATH/$FILE –data-binary @localfile example : $ curl -v –user username:password –data-binary @local-file -X PUT “http://<artifactory server >/artifactory/abc-snapshot-local/remotepath/remotefile”
This is easily achieved by revoking the “Delete” permission from the deploying users\groups on the target repository; the delete permission is required for both artifact removal and artifact re-deployment. All user\group permissions are editable within the UI at Admin->Security->Permissions. Also see Managing Permissions
You need to add an ivysettings.xml file with the following repositories listed (resolvers in ivy speak) <ivysettings> <settings defaultResolver=”chain”/> <resolvers> <chain name=”chain”> <ibiblio name=”central” m2compatible=”true”/> <ibiblio name=”example” m2compatible=”true” root=”http://example.com/m2/”/> </chain> </resolvers> </ivysettings> In my opinion it makes more sense to separate the dependency declaration (ivy.xml) from the mechanism of retrieval (settings.xml). This is not needed … Read more