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

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

jira-importer opened a new issue, #669:
URL: https://github.com/apache/maven-scm/issues/669

   **[Mark 
Struberg](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=struberg)**
 opened 
**[SCM-458](https://issues.apache.org/jira/browse/SCM-458?redirect=false)** and 
commented
   
   The current git changelog implementation always reports the changelog of the 
full repo.
   
   This doesn't make sense for multi-module projects since reporting the 
changelog only for a single child artifact is not possible yet.
   
   This can be changed if we always apply a '

> GitChangeLogCommand always reports over the whole git repo - also for child 
> modules
> -----------------------------------------------------------------------------------
>
>                 Key: SCM-458
>                 URL: https://issues.apache.org/jira/browse/SCM-458
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.1
>            Reporter: Mark Struberg
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 1.3
>
>         Attachments: SCM-458.patch
>
>
> The current git changelog implementation always reports the changelog of the 
> full repo. 
> This doesn't make sense for multi-module projects since reporting the 
> changelog only for a single child artifact is not possible yet.
> This can be changed if we always apply a '-- ${basedir} for each 
> git-whatchanged invocation.



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

Reply via email to