Re: Getting a 401 when trying to upload my plugin to Artifactory

It's been a couple weeks so I thought I would check in. I'm still unable to finish the maven release: perform step. On Apr 16, 2017 9:46 PM, "Adam Chevalier" wrote: I added a distributionManagement node (copied the one found in the accurev plugin <https://github.com/j

Re: Getting a 401 when trying to upload my plugin to Artifactory

017 at 9:36 PM, Adam Chevalier wrote: > My pom had not distribution node, this is probably the issue. I'll test it > quick and let you know. > > On Sun, Apr 16, 2017 at 9:32 PM, Adam Chevalier > wrote: > >> I've attached my effective pom and maven settings with

Re: Getting a 401 when trying to upload my plugin to Artifactory

My pom had not distribution node, this is probably the issue. I'll test it quick and let you know. On Sun, Apr 16, 2017 at 9:32 PM, Adam Chevalier wrote: > I've attached my effective pom and maven settings with passwords removed. > Mark, I'll compare my destination with

Re: Getting a 401 when trying to upload my plugin to Artifactory

I've attached my effective pom and maven settings with passwords removed. Mark, I'll compare my destination with other plugins, thanks for the suggestion. On Sun, Apr 16, 2017 at 4:20 PM, Daniel Beck wrote: > > > On 16.04.2017, at 22:34, Adam Chevalier > wrote: >

Getting a 401 when trying to upload my plugin to Artifactory

Hi, I'm trying to deploy my plugin (testrail-plugin) to the Jenkins Artifactory and keep getting 401s. I get the following error http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [INFO] [INFO] BUILD

Re: Maven says it can't find MasterToSlaveFileCallable

at is actually being used. On Tue, Nov 29, 2016 at 8:29 AM, Jesse Glick wrote: > On Mon, Nov 28, 2016 at 7:58 PM, Adam Chevalier > wrote: > > I determined that MasterToSlaveFileCallable was the best fit for the > > intent. However, maven is telling me it can't find that

Maven says it can't find MasterToSlaveFileCallable

I'm working on getting this plugin ready for hosting and I've had some problems after updating the parent pom version to 2.6 The first two rounds of compilation errors were resolved by updating some dependencies, but then I had to replace a us