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

2018-11-03 Thread Mirko Friedenhagen
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. Best Regards Mirko Friedenhagen — Sent from my mobile Am 03.11.18 um 17:55 schrieb Mark Raynsford > Hello. > > If I want to deploy to a

Specifying a deployment repository *only* by ID?

2018-11-03 Thread Mark Raynsford
Hello. If I want to deploy to a different repository, I can use the http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#altDeploymentRepository property: $ mvn deploy -DaltDeploymentRepository=releases::default::https://packages.example.com/repository/releases This is

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

2018-11-03 Thread Robert Scholte
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 value explicit in the pom file. Robert On Sat, 03 Nov 2018 12:36:30 +0100, Karl Heinz Marbaise wrote: Hi Hervé, On 03/11/18

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

2018-11-03 Thread Karl Heinz Marbaise
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 it should not be complex on our side If its that simple we should do that... But on the

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

2018-11-03 Thread Hervé BOUTEMY
yes, sorry... I already marked MNG-6059 as "fix for: 3.6.1" I suppose we should fix also the compatibility issue with IntelliJ, since it should not be complex on our side Regards, Hervé Le vendredi 2 novembre 2018, 06:17:06 CET Karl Heinz Marbaise a écrit : > Hi, > > On 01/11/18 23:55,