[
https://jira.codehaus.org/browse/ARCHETYPE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340270#comment-340270
]
Baptiste Mathus edited comment on ARCHETYPE-456 at 1/27/14 3:28 PM:
--------------------------------------------------------------------
New version of the patch.
Not sure at all though that the patch format is gonna retain the necessarily
different newline encodings (LF, CR instead of a single one and so on). So, I'm
also attaching a zipped version of the new it directory.
The ITs is actually composed of two runs, the first one *must* fail (without
enabling the ignoreEOLEncoding new behaviour).
was (Author: baptiste):
New version of the patch.
Not sure at all though that the patch format is gonna retain the necessary
newline encoding (LF, CR instead of a single one and so on). So, I'm also
attaching a zipped version of the new it directory.
The ITs is actually composed of two runs, the first one *must* fail (without
enabling the ignoreEOLEncoding new behaviour).
> Add an option to allow comparing reference project to generated one
> regardless of the EOL encoding
> --------------------------------------------------------------------------------------------------
>
> Key: ARCHETYPE-456
> URL: https://jira.codehaus.org/browse/ARCHETYPE-456
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 2.2
> Reporter: Baptiste Mathus
> Attachments: ARCHETYPE-ignoreEOLEncoding-v2.patch,
> build-archetype-ignore-eol-encoding.zip
>
>
> Mojo : archetype:integration-test
> Currently, depending on where you created the reference project to be
> compared to the generated one, the test can fail.
> This feature would add an option to ask for comparison saying basically you
> don't care it's a CR, a LF, or a CRLF EOL, and are only interested in the
> rest of the content.
> I'm also including a patch (which also includes the corresponding IT for the
> invoker-plugin).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
