[ 
https://issues.apache.org/jira/browse/SCM-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963150#comment-17963150
 ] 

ASF GitHub Bot commented on SCM-801:
------------------------------------

jira-importer commented on issue #1027:
URL: https://github.com/apache/maven-scm/issues/1027#issuecomment-2964639792

   **[Hervé 
Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)**
 commented
   
   1. if the solution asked is to add a field to the POM and change inheritance 
algorithm, this issue has to be changed into MNG (I documented and unit-tested 
everything lately: see 
http://maven.apache.org/ref/3-LATEST/maven-model-builder/ and 
http://maven.apache.org/ref/3-LATEST/maven-model-builder/testapidocs/src-html/org/apache/maven/model/inheritance/DefaultInheritanceAssemblerTest.html#line.40
   
   2. if the solution is to make Maven Project Info Reports Plugin display 
fixed information, it was done in MPIR version 2.8: see MPIR-290
   
   3. if you know plugins/tools other than Maven Project Info Reports Plugin 
reading information from POM and having the issue, please name them, that will 
help me understand who I have to explain the problem
   
   4. IMHO, the right fix would be in SCM (with this Jiea issue) by adding a 
new "path" field in git scm url: plugins using the SCM API to parse the scm url 
would have the right repo url when asking for repo and could get the path 
inside the repo using a new "getPath()" API
   
   




> Correct SCM URLs mangled in children
> ------------------------------------
>
>                 Key: SCM-801
>                 URL: https://issues.apache.org/jira/browse/SCM-801
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>            Reporter: Caleb Cushing
>            Priority: Major
>
> http://stackoverflow.com/a/26753032/206466
> a lot of git repositories require the repository name to end it .git, only 
> for a few services could this configuration ever be correct.
> Because I know asking for the behavior to stop auto appending would break 
> backwards compatibility, instead I'd like to see a field added that would 
> allow us to override the behavior, so that we don't have to duplicate this 
> section in every sub pom.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to