Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2.1.0
-
Fix Version/s: Issues to be reviewed for 3.x
-
Component/s: POM
-
Labels:None
-
Complexity:Intermediate
Description
Right now, the encoding used for filtering resources is a config parameter of the Resources Plugin. This gets problematic when the resource files employ different encodings. So the natural solution is to recognize file encoding as an intrinsic property of resources and lift it to the model itself.
Issue Links
- is related to
-
MNG-2216
Add default encodings section to POM
-
- relates to
-
MRESOURCES-88
Allow specific encoding per group of files
-