[ http://jira.codehaus.org/browse/MINVOKER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MINVOKER-30: -------------------------------------- Description: Right now, the {{verify.bsh}} is read using the platform's default encoding, making the tests platform-dependent. We should enrich the plugin configuration to allow the user to lock down the encoding and ensure reproducible tests. The same applies to the {{goals.txt}} and {{profiles.txt}}. was: Right now, the {{verify.bsh}} is read using the platform's default encoding, making the tests platform-dependent. We should enrich the plugin configuration to allow the user to lock down the encoding and ensure reproducible tests. The same applies to the {{goals.txt}}. Patch Submitted: [Yes] Attachment: file-encoding.patch Here is the proposed patch, following our current proposal about [source file encoding|http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding]. > Allow to configure file encoding for verifications scripts > ---------------------------------------------------------- > > Key: MINVOKER-30 > URL: http://jira.codehaus.org/browse/MINVOKER-30 > Project: Maven 2.x Invoker Plugin > Issue Type: Improvement > Affects Versions: 1.1 > Reporter: Benjamin Bentmann > Attachments: file-encoding.patch > > > Right now, the {{verify.bsh}} is read using the platform's default encoding, > making the tests platform-dependent. We should enrich the plugin > configuration to allow the user to lock down the encoding and ensure > reproducible tests. > The same applies to the {{goals.txt}} and {{profiles.txt}}. -- 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