You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/03/15 00:16:28 UTC
[jira] Created: (MPLUGIN-101) Allow customization of file encoding
used for mojo extraction
Allow customization of file encoding used for mojo extraction
-------------------------------------------------------------
Key: MPLUGIN-101
URL: http://jira.codehaus.org/browse/MPLUGIN-101
Project: Maven 2.x Plugin Tools
Issue Type: Improvement
Components: API, Java Plugins, Plugin Plugin
Affects Versions: 2.3
Reporter: Benjamin Bentmann
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPLUGIN-101) Allow customization of file encoding
used for mojo extraction
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MPLUGIN-101.
------------------------------
Resolution: Fixed
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.
> Allow customization of file encoding used for mojo extraction
> -------------------------------------------------------------
>
> Key: MPLUGIN-101
> URL: http://jira.codehaus.org/browse/MPLUGIN-101
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: API, Beanshell Plugins, Java Plugins, Plugin Plugin
> Affects Versions: 2.3
> Reporter: Benjamin Bentmann
> Assignee: John Casey
> Fix For: 2.5
>
> Attachments: source-file-encoding.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-101) Allow customization of file encoding
used for mojo extraction
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton updated MPLUGIN-101:
------------------------------------
Fix Version/s: 2.5
> Allow customization of file encoding used for mojo extraction
> -------------------------------------------------------------
>
> Key: MPLUGIN-101
> URL: http://jira.codehaus.org/browse/MPLUGIN-101
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: API, Beanshell Plugins, Java Plugins, Plugin Plugin
> Affects Versions: 2.3
> Reporter: Benjamin Bentmann
> Fix For: 2.5
>
> Attachments: source-file-encoding.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-101) Allow customization of file encoding
used for mojo extraction
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MPLUGIN-101:
--------------------------------------
Attachment: source-file-encoding.patch
> Allow customization of file encoding used for mojo extraction
> -------------------------------------------------------------
>
> Key: MPLUGIN-101
> URL: http://jira.codehaus.org/browse/MPLUGIN-101
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: API, Beanshell Plugins, Java Plugins, Plugin Plugin
> Affects Versions: 2.3
> Reporter: Benjamin Bentmann
> Attachments: source-file-encoding.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPLUGIN-101) Allow customization of file encoding
used for mojo extraction
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPLUGIN-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MPLUGIN-101:
--------------------------------------
Component/s: Beanshell Plugins
Patch Submitted: [Yes]
> Allow customization of file encoding used for mojo extraction
> -------------------------------------------------------------
>
> Key: MPLUGIN-101
> URL: http://jira.codehaus.org/browse/MPLUGIN-101
> Project: Maven 2.x Plugin Tools
> Issue Type: Improvement
> Components: API, Beanshell Plugins, Java Plugins, Plugin Plugin
> Affects Versions: 2.3
> Reporter: Benjamin Bentmann
> Attachments: source-file-encoding.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira