[MEJB-65] Upgrade maven-filtering to 1.2

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3
• Fix Version/s: 2.4
• Assignee: Karl Heinz Marbaise
• Reporter: Karl Heinz Marbaise
• Created: 08/Aug/14 08:50
• Updated: 26/Aug/14 20:02
• Resolved: 08/Aug/14 09:15

Description

Currently maven-ejb uses maven-filtering 1.0 we should upgrade to newer version

Release Notes - Maven Shared Components - Version maven-filtering-1.1

• • Bug
• MSHARED-195 - maven-filtering incorrect states a dependency to maven-monitor
• MSHARED-215 - maven-filtering brings in JUnit as transitive dependency
• MSHARED-223 - NullPointerException in maven-resources-plugin
• MSHARED-228 - MultiDelimiterInterpolatorFilterReaderLineEnding() does not filter after a token is escaped

Release Notes - Maven Shared Components - Version maven-filtering-1.2

• • Bug
• MSHARED-161 - DefaultMavenFileFilter.getDefaultFilterWrappers loads filters from the current directory instead of using basedir
• MSHARED-198 - custom delimiters doesn't work as expected
• MSHARED-199 - Filtering doesn't work if 2 delimiters are used on the same line, the first one being left open
• MSHARED-319 - Filtering throws NPE when using JDK8

• • New Feature
• MSHARED-220 - Apply filtering to filenames