What's the difference between sonar.links.scm and sonar.links.scm_dev?

jochen.haag · February 15, 2019, 11:32am

Hello SonarSource community,

I would like to understand the difference between the two link properties:

sonar.links.scm
sonar.links.scm_dev

The documentation does not give much input except for:

sonar.links.scm = Project source repository.
sonar.links.scm_dev = Developer connection.

Unfortunately I have no idea what the term developer connection stands for.

Can you please share your thoughts?

Thanks a lot!

Scott · February 15, 2019, 12:11pm

Hi.

You can ignore sonar.links.scm_dev, just use sonar.links.scm:

github.com

SonarSource/sonarqube/blob/4e94db27ded24dbe907970c21a96e75f8d581a33/sonar-plugin-api/src/main/java/org/sonar/api/CoreProperties.java#L340-L345


      
          /**
           * @since 3.3
           * @deprecated since 7.1, developer connection link is no more feed
           */
          @Deprecated
          String LINKS_SOURCES_DEV = "sonar.links.scm_dev";

I think it was inherited from Maven definitions:

connection , developerConnection : The two connection elements convey to how one is to connect to the version control system through Maven. Where connection requires read access for Maven to be able to find the source code (for example, an update), developerConnection requires a connection that will give write access.

jochen.haag · February 15, 2019, 4:10pm

Thanks for the clarification!

jochen.haag · February 19, 2019, 11:31am

Hi @ganncamp,
Will the documentation be updated accordingly by moving sonar.links.scm_dev to the deprecated section?

ganncamp · February 19, 2019, 1:26pm

Uhmm… Why yes. Yes, of course it will be!

Thanks for the nudge. This will appear in the docs at the next release.

Ann