Setting the developerConnection for the Maven Release Plugin from the command line

Question

I am currently trying to configure the Maven Release Plugin for our build server.

For that I am trying to set the <scm><developerConnection> through the command line. I read that

project.scm.developerConnection

is the command line property(https://maven.apache.org/guides/mini/guide-releasing.html). I tried to set it but it seems to have no effect. When I start the build, it uses a constructed URL (parent pom url + artifactId) that fails.

I have looked at the source code of the plugin but did not find the command line property mentioned above.

Can anybody shed light on this?

I used `mvn release:prepare -Dproject.scm.developerConnection=...` — J Fabian Meier, Dec 05 '18 at 19:18

score 4 · Answer 1 · answered Jan 18 '19 at 09:16

It looks that you cannot pass this property directly from command line. See:

https://issues.apache.org/jira/browse/MRELEASE-707

But you should get it working by specifying it through a custom property in your pom.xml:

<properties>
    <my.developer.connection />
</properties>

<scm>
    <developerConnection>${my.developer.connection}</developerConnection>
    <tag>HEAD</tag>
</scm>

And running maven with, for example:

-Dmy.developer.connection=scm:git:ssh://user@host/repo.git

I use this approach to keep my pom.xml clean when generating a public release that should not contain information about my company's internals.

user944849 · Answer 2 · 2018-12-06T17:22:20.773

1

When you run mvn release:prepare, Maven forks. The arguments supplied on the command line are passed to the initial Maven call (the one you/build server ran) not to the fork.

To pass args to the release plugin, supply the arguments as shown:

mvn release:prepare -Darguments="-Dproject.scm.developerConnection=..." ...

Depending on what I'm trying to do, sometimes I've had to specify in two places, so both original and forked processes get the args:

mvn release:prepare -DsomeArg=val -Darguments="-DsomeArg=val" ...

The first example in the release plugin FAQ shows an example of where the latter is useful.

---- Update ----

I found the property in the maven-scm-plugin code.

Maybe project.scm.developerConnection is read-only? Try setting scmDeveloperConnection instead, as it's listed as the property name.

edited Dec 06 '18 at 17:22

answered Dec 05 '18 at 19:43

user944849

14,524
2
61
83

Thank you, but no luck so far. – J Fabian Meier Dec 06 '18 at 09:35
Have you tried running with debug (`-X`)? Might need to specify it in two places. Maybe that will give a clue. – user944849 Dec 06 '18 at 16:45
Yes, but did not see anything. Still confused about this issue. – J Fabian Meier Dec 06 '18 at 17:13
Tried this as well, also with a new project, but no luck. Also tried to change `tagBase`, but this only changes the destination, not the source, so it does not work either. – J Fabian Meier Dec 07 '18 at 12:06
Thank you so much for the -Darguments suggestion! Azure pipeline required it to be annotated like that for some reason – David S Mar 23 '22 at 07:34

Setting the developerConnection for the Maven Release Plugin from the command line

2 Answers2