You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Slawomir Jaranowski (Jira)" <ji...@apache.org> on 2024/09/14 08:22:00 UTC

[jira] [Commented] (ARCHETYPE-632) Add logging conflict line in integration-test

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

Slawomir Jaranowski commented on ARCHETYPE-632:
-----------------------------------------------

PR to refresh

> Add logging conflict line in integration-test
> ---------------------------------------------
>
>                 Key: ARCHETYPE-632
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-632
>             Project: Maven Archetype
>          Issue Type: Improvement
>          Components: Plugin
>    Affects Versions: 3.2.1
>            Reporter: Toshiya Kobayashi
>            Priority: Major
>             Fix For: 3.3.0
>
>
> In maven-archetype-plugin integration-test phase, if a generated file is not equal to a reference file, WARNING is raised
> {noformat}
> [WARNING] Contents of file src/test/java/it/pkg/RuleTest.java are not equal
> {noformat}
> But sometimes it's hard to locate where the conflict line is.
> This JIRA is to log more information like:
> {noformat}
> [WARNING] Conflict found. Reference line :
> [WARNING]     private static final Logger LOG = LoggerFactory.getLogger(RuleTest.class);
> [WARNING] Actual line :
> [WARNING]     static final Logger LOG = LoggerFactory.getLogger(RuleTest.class);
> [WARNING] Contents of file src/test/java/it/pkg/RuleTest.java are not equal
> {noformat}



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