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

["Sylwester Lachiewicz (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylwester Lachiewicz closed MRESOURCES-273.
-------------------------------------------
    Resolution: Fixed

Done in [680717c7d3c5a1f3f7891b923cfa8e0a55eb03d3|https://gitbox.apache.org/repos/asf?p=maven-filtering.git;a=commit;h=680717c7d3c5a1f3f7891b923cfa8e0a55eb03d3] 

> 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
>            Assignee: Sylwester Lachiewicz
>            Priority: Critical
>             Fix For: 3.3.0
>
>
> 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.20.1#820001)