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

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

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

   **[Jean-Pierre 
Matsumoto](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jpmat296)**
 opened 
**[SCM-332](https://issues.apache.org/jira/browse/SCM-332?redirect=false)** and 
commented
   
   When I call mvn changelog:changelog on my Perforce project, I get one entry 
in changelog for each couple (changelist,file) instead of one entry for each 
changelist.
   
   I have a patch to solve this bug. I group relevant entries.
   
   I updated existing TestCase. And I tested on my project and the bug is 
solved with this patch.
   
   
   ---
   
   **Affects:** 1.1
   
   **Attachments:**
   - 
[p4-group_entries.patch](https://issues.apache.org/jira/secure/attachment/12718502/p4-group_entries.patch)
 (_2.97 kB_)
   
   1 votes, 1 watchers
   




> Perforce provider give one changeset entry for each file
> --------------------------------------------------------
>
>                 Key: SCM-332
>                 URL: https://issues.apache.org/jira/browse/SCM-332
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-perforce
>    Affects Versions: 1.1
>         Environment: MacOSX
>            Reporter: Jean-Pierre Matsumoto
>            Assignee: Olivier Lamy
>            Priority: Major
>             Fix For: 1.2
>
>         Attachments: p4-group_entries.patch
>
>
> When I call mvn changelog:changelog on my Perforce project, I get one entry 
> in changelog for each couple (changelist,file) instead of one entry for each 
> changelist.
> I have a patch to solve this bug. I group relevant entries.
> I updated existing TestCase. And I tested on my project and the bug is solved 
> with this patch.



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

Reply via email to