artifactory

Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity): https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz ?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz Then, from pull request to pull requests, these dl parameters constantly oscillate to being present or removed depending on which

Locally on the machine i have an Artifactory installed with maven repositories, and i have a very simple .pom file for my project which points to it: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>MYGROUP</groupId> <artifactId>NAME</artifactId> <packaging>jar</packaging> <version>VERSION</version> <build> <sourceDirectory>SRCFOLDER</sourceDirectory> <testSourceDirectory>TESTFOLDER<

I am trying to introduce decent reference management to my organisation. Having used Nexus with Maven before, I know it to be far superior to the method of building everything locally. As this is a .Net shop I want to use NuGet instead of Maven. I know the binary repository will be the most important bit to get right, but have no experience of hosting a NuGet repository in a binary repository. Is there any reason to favour Nexus or Artifactory in this situation? We are using Jenkins with svn as our CI, if that makes any difference. Yoav Landman This is what we found out last time we compared

Currently I have a Maven2 project that builds a JAR when you run: mvn clean package I need to now tweak the pom.xml to publish this JAR ( myapp.jar ) to an Artifactory server running at: http://myartifactory/artifactory/simple/myorg/myapp/0.1 I tried adding a <repositories> element to my pom.xml but nothing is being published with this config: <repositories> <repository> <id>myartifactory</id> <url>http://myartifactory/artifactory/simple/</url> </repository> </repositories> Any ideas as to how I could get publishing to work? For simplicity's sake, pretend that this Artifactory repo is

I have an Artifactory repo that sits behind basic authentication. How would I configure the settings.xml to allow access? <mirrors> <mirror> <id>artifactory</id> <mirrorOf>*</mirrorOf> <url>https://myserver.example.com/artifactory/repo</url> <name>Artifactory</name> </mirror> </mirrors> <servers> <!-- This server configuration gives your personal username/password for artifactory. Note that the server id must match that given in the mirrors section. --> <server> <id>Artifactory</id> <username>someArtifactoryUser</username> <password>someArtifactoryPassword</password> </server> So server tag is

This seemed to be working last week and now it doesn't. We use Artifactory as our Maven repository. I am deploying a jar and pom using the deploy:deploy-file goal Our Artifactory repository requires authentication to deploy. I can deploy to the repository by embedding my credentials in the server URL on the command line: $ mvn deploy:deploy-file \ -Durl=http://deployer:swordfish@repo.veggiecorp.com/artifactory/ext-release-local \ -Dfile=crypto.jar \ -DpomFile=pom.xml \ -Did=VeggieCorp yadda...yadda...yadda... [INFO] ------------------------------------------------------------------------ [INFO

As part of an automated deployment I need a script to download the latest version of an artifact from our internal repository. Ideally this script will be with ant or a unix shell script. So for example: I have myArtifact.war and it has versions 1.0 , 1.1 and 2.0 - I need the script given the correct group id and artifact id to retrieve version 2.0 from our maven repository (currently using artifactory). Is there any easy way to do this? Rich Seller You can parse the maven-metadata.xml to see what versions are available, and which version is the "release" version. See this answer about plugin