Re: Username/password not sent for altDeploymentRepository?

2018-11-04 Thread Mirko Friedenhagen
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 bee

Re: Username/password not sent for altDeploymentRepository?

2018-11-04 Thread Mark Raynsford
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 io7m.u

Re: mvn --version (java inconsistency?)

2018-11-04 Thread Stuart McCulloch
I believe that's true for the current releases, but it looks like it will change in the future: https://github.com/AdoptOpenJDK/openjdk-build/issues/465 On Sun, 4 Nov 2018 at 19:46, Elliot Huntington wrote: > Now that Oracle is charging licensing fees to use Oracle Java as of Java > 11, I am swi

mvn --version (java inconsistency?)

2018-11-04 Thread Elliot Huntington
Now that Oracle is charging licensing fees to use Oracle Java as of Java 11, I am switching to Open JDK. Here is the output for my environment configuration in case it is helpful. Everything looks consistent to me except the bold output which lists Oracle as the java vendor. Is Oracle listed as th

Re: Username/password not sent for altDeploymentRepository?

2018-11-04 Thread Mark Raynsford
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 > 2018

Username/password not sent for altDeploymentRepository?

2018-11-04 Thread Mark Raynsford
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 u

Re: PSA: You can't push POMs with child.inherit.append.path attributes to Maven Central yet

2018-11-04 Thread Hervé BOUTEMY
good idea, that's a good opportunity: let's try Regards, Hervé Le samedi 3 novembre 2018, 13:01:34 CET Robert Scholte a écrit : > I could start experimenting with this specific issue. > > Maven 3.6.0 has access to a FileTransformer, which can be used to make > remove this attribute and make its

Re: PSA: You can't push POMs with child.inherit.append.path attributes to Maven Central yet

2018-11-04 Thread Hervé BOUTEMY
Le samedi 3 novembre 2018, 12:36:30 CET Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 03/11/18 12:29, Hervé BOUTEMY wrote: > > yes, sorry... > > No problem.. > > > I already marked MNG-6059 as "fix for: 3.6.1" > > > > I suppose we should fix also the compatibility issue with IntelliJ, since

Re: Specifying a deployment repository *only* by ID?

2018-11-04 Thread Mark Raynsford
On 2018-11-04T00:24:46 +0100 "Mirko Friedenhagen" wrote: > Hello Mark, > > you may put the property in a profile of your settings.xml and just call „mvn > -P releases deploy“ given the profile is called releases. Ah, yes, thank you! Didn't think of that. -- Mark Raynsford | http://www.io7m.c