Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.3
-
Fix Version/s: 2.5
-
Component/s: API, maven-plugin-tools-beanshell, maven-plugin-tools-java, Plugin Plugin
-
Labels:None
-
Patch Submitted:Yes
-
Number of attachments :
Description
Right now, the user has no chance to configure the file encoding used when scanning the source tree for mojos at the POM level, e.g. QDox's JavaDocBuilder simply uses the JVM's default encoding. For smooth and reproducible builds in a Non-ASCII world, the plugin needs an "encoding" parameter to pass around into the MojoScanner and finally into the various MojoDescriptorExtractor's.
Issue Links
- depends upon
-
MPLUGIN-110
Make easier to pass parameters into MojoDescriptorExtractors
-
- is depended upon by
-
MPLUGIN-111
Warn about usage of platform encoding
-
- is related to
-
MNG-2216
Add default encodings section to POM
-
- relates to
-
MPLUGIN-100
Allow customization of file encoding used for generated help goal
-
I've added the encoding parameter to the new PluginToolsRequest interface/default impl. instead of making it a direct parameter of each method within the plugin tools. This should make it easier to get that parameter to the places where it might be needed.