[
https://issues.apache.org/jira/browse/MRESOURCES-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264926#comment-17264926
]
Elias Balasis commented on MRESOURCES-273:
------------------------------------------
Thanks for clarifying,
it would be great if this can be fixed in a future version, otherwise we will
be permanently locked to 2.6 which as you can understand is not a good practice
plus shortening our Maven variables is completely unaffordable for us.
> 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)
