Conversation
| <tag>HEAD</tag> | ||
| <url>https://github.com/codehaus-plexus/plexus-sec-dispatcher.git</url> | ||
| <connection>scm:git:https://github.com/codehaus-plexus/plexus-sec-dispatcher.git</connection> | ||
| <developerConnection>scm:git:ssh://git@github.com:codehaus-plexus/plexus-sec-dispatcher.git</developerConnection> |
There was a problem hiding this comment.
Do we use SSH or HTTPs authentication here?
There was a problem hiding this comment.
I see https in more of plexus project
There was a problem hiding this comment.
It is IMHO a hassle with GitHub as it requires using PAT (https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/about-authentication-to-github#https).
There was a problem hiding this comment.
Make it work with SSH as before, as HTTPS is meh. I have same issue on ASF projects as well, HTTPS gitbox keeps asking me for username and pw, unlike when using SSH.
There was a problem hiding this comment.
There were some concerns in the past regarding blocked SSH ports. For me there is a fundamental difference between Gitbox and GitHub: The former allows to use your regular credentials, the latter requires a PAT.
There was a problem hiding this comment.
If you want to change start from - parent pom .... mixed can have impact of relative path calculation by site plugin 😄
There was a problem hiding this comment.
This is no longer the case with an upcoming version of maven-site-plugin: apache/maven-site-plugin#227
| <scm> | ||
| <connection>scm:git:git@github.com:codehaus-plexus/plexus-sec-dispatcher.git</connection> | ||
| <developerConnection>scm:git:git@github.com:codehaus-plexus/plexus-sec-dispatcher.git</developerConnection> | ||
| <tag>HEAD</tag> |
Use proper SSH URL for developerConnection, use HTTPs for regular connection
Use proper SSH URL for developerConnection, use HTTPs for regular connection