[Comment Edited] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Comment Edited] (MRESOURCES-273) Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0

Herve Boutemy (Jira)

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

Piotr Zygielo edited comment on MRESOURCES-273 at 1/14/21, 11:50 AM:
---------------------------------------------------------------------

With above reproducer m-resources-p bisected to [ceaab5c9c468c34fc9a2381f2787bc53516e70e3|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commit;h=ceaab5c9c468c34fc9a2381f2787bc53516e70e3] (MRESOURCES-192).

Overriding/reverting this dependency in plugin back to 1.2 helps. Using the newest maven-filtering:3.2.0 - does not.

 


was (Author: pzygielo):
With above reproducer m-resources-p bisected to [ceaab5c9c468c34fc9a2381f2787bc53516e70e3|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commit;h=ceaab5c9c468c34fc9a2381f2787bc53516e70e3] (MRESOURCES-192).

> Filtering of Maven properties with long names is not working after transition from 2.6 to 3.2.0
> -----------------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-273
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-273
>             Project: Maven Resources Plugin
>          Issue Type: Bug
>          Components: filtering
>    Affects Versions: 3.2.0
>            Reporter: Elias Balasis
>            Priority: Critical
>             Fix For: waiting-for-feedback
>
>
> In my team, part of a large global organization, we have upgraded from 2.6 to 3.2.0
> but only to discover that 3.2.0 is not filtering Maven properties with long names anymore.
> The particular Maven property which wasn't filtered is 148 characters long.
> This has never been a problem with 2.6 though.
> It is implied that a breaking change has been made after 2.6 which now prevents us from upgrading.
> We are temporarily reverting to 2.6 but only temporarily.
> Equally, the cost of reducing the length of the associated Maven properties is not affordable and we will not apply such a workaround.
> Please revert the broken functionality.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)