[
https://issues.apache.org/jira/browse/SCM-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961011#comment-17961011
]
ASF GitHub Bot commented on SCM-332:
------------------------------------
jira-importer commented on issue #542:
URL: https://github.com/apache/maven-scm/issues/542#issuecomment-2964601804
**[Peter
Janes](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=peterj)**
commented
I understand from SCM-155 that there isn't a Perforce server to test this
against. In its stead, I can confirm from a second source (OS=Linux, p4d
2007.3, p4 2008.1) that this patch works as advertised. It would be nice to
see it incorporated into a released version.
> 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)
