On 2018-11-04T23:16:31 +0100
"Mirko Friedenhagen" wrote:
> Maybe you run into
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/MDEPLOY-244.
> maven-deploy-Plugin 3.0x has a slightly different syntax for specifying
> alt*Repositories.
>
Ouch! Yes, that would explain it. I did
Maybe you run into
https://issues.apache.org/jira/plugins/servlet/mobile#issue/MDEPLOY-244.
maven-deploy-Plugin 3.0x has a slightly different syntax for specifying
alt*Repositories.
Best Regards
Mirko Friedenhagen
—
Sent from my mobile
Am 04.11.18 um 22:47 schrieb Mark Raynsford
> I've
I've been completely unable to get this work. It seems like
altDeploymentRepository just doesn't pick up credentials for whatever
reason.
I've instead taken this approach: In my organization-wide POM, I've
added a profile:
io7m-alternate-repository
On 2018-11-04T12:30:32 +
Mark Raynsford wrote:
>
> 2018-11-04 12:14:16,266 [qtp367589601-760] INFO
> org.apache.archiva.security.ArchivaServletAuthenticator [] - Authorization
> Denied [ip=10.2.4.1,permission=archiva-upload-repository,repo=arc7-releases]
> : no matching permissions
>
Hello!
As is probably obvious from my other questions, I'm currently setting up
a local repository manager (Apache Archiva in this instance) used to
deploy internal releases (things that won't make it to Central), and to
act as a proxy for Central for my local network.
Archiva appears to be set