[jira] Created: (MECLIPSE-160) Wrong description with the goal add-maven-repo documentation
Wrong description with the goal add-maven-repo documentation -- Key: MECLIPSE-160 URL: http://jira.codehaus.org/browse/MECLIPSE-160 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Reporter: Naoki Nose The plugin documentation says the goal eclipse:add-maven-repo adds the classpath variable MAVEN_REPO to Eclipse. But that goal adds the variable M2_REPO actually. -- 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] Created: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
the encoding parameter in xml declaration of POM is ignored Key: MNG-2254 URL: http://jira.codehaus.org/browse/MNG-2254 Project: Maven 2 Type: Bug Reporter: Naoki Nose Attachments: modello-plugin-xpp3.diff DefaultMavenProjectBuilder reads POM in system default character encoding, and the encoding parameter in xml declartion is ignored. to fix this problem, We should - fix modello-plugin-xpp3 to use the xml parser which is able to handle the encoding parameter properly - regenerate maven-model using fixed modello-plugin-xpp3 - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- 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: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=all ] Naoki Nose updated MNG-2254: Attachment: DefaultMavenProjectBuilder.diff the encoding parameter in xml declaration of POM is ignored Key: MNG-2254 URL: http://jira.codehaus.org/browse/MNG-2254 Project: Maven 2 Type: Bug Reporter: Naoki Nose Attachments: DefaultMavenProjectBuilder.diff, modello-plugin-xpp3.diff DefaultMavenProjectBuilder reads POM in system default character encoding, and the encoding parameter in xml declartion is ignored. to fix this problem, We should - fix modello-plugin-xpp3 to use the xml parser which is able to handle the encoding parameter properly - regenerate maven-model using fixed modello-plugin-xpp3 - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- 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] Commented: (MNG-2254) the encoding parameter in xml declaration of POM is ignored
[ http://jira.codehaus.org/browse/MNG-2254?page=comments#action_64373 ] Naoki Nose commented on MNG-2254: - Attached files are the patch to fix this issue. These files depend on the patch of MXParser which I attached to the following issue. http://jira.codehaus.org/browse/MNG-2148 using a external standard xml pull parser may be better solution, as discussed in the following issue. http://jira.codehaus.org/browse/DOXIA-60 the encoding parameter in xml declaration of POM is ignored Key: MNG-2254 URL: http://jira.codehaus.org/browse/MNG-2254 Project: Maven 2 Type: Bug Reporter: Naoki Nose Attachments: DefaultMavenProjectBuilder.diff, modello-plugin-xpp3.diff DefaultMavenProjectBuilder reads POM in system default character encoding, and the encoding parameter in xml declartion is ignored. to fix this problem, We should - fix modello-plugin-xpp3 to use the xml parser which is able to handle the encoding parameter properly - regenerate maven-model using fixed modello-plugin-xpp3 - fix DefaultMavenProjectBuilder to use regenerated maven-model properly. -- 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: (MNG-2148) MXParser can't handle the encoding declaration in XML declaration
[ http://jira.codehaus.org/browse/MNG-2148?page=all ] Naoki Nose updated MNG-2148: Attachment: plexus-utils.diff MXParser can't handle the encoding declaration in XML declaration -- Key: MNG-2148 URL: http://jira.codehaus.org/browse/MNG-2148 Project: Maven 2 Type: Bug Components: POM Reporter: Naoki Nose Attachments: plexus-utils.diff, src.jar The xml pull parser in plexus-utils(MXParser.java) can't handle the encoding declaration in XML declaration. So, it's impossible to use an encoding different from system default encoding. This is critical in Japan, because there is two commonly used encodings in Japanese environment(SJIS and EUC-JP). I think MXParser should handle encoding declaration in xml as described in w3c specification/ http://www.w3.org/TR/REC-xml/#sec-guessing I tried to fix this problem(see attachment). I changed the setInput(InputStream) method to detect encoding in xml declaration. For writing this code, I referred to source code of Apache Xerces. UCS-4 and UCS-2 isn't supported in this implementation, because these encoding isn't supported by Sun JDK. Xerces solves this problem by providing original reader for these encodings. I think Xerces's solution is too complex for plexus-utils. To solve this issue, it's not sufficient only to change plexus-utils, because DefaultMavenProjectBuilder reads POM by FileReader without specifying encoding. -- 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: (MNG-2148) MXParser can't handle the encoding declaration in XML declaration
[ http://jira.codehaus.org/browse/MNG-2148?page=all ] Naoki Nose updated MNG-2148: Attachment: plexus-utils-test-resource.tar.gz MXParser can't handle the encoding declaration in XML declaration -- Key: MNG-2148 URL: http://jira.codehaus.org/browse/MNG-2148 Project: Maven 2 Type: Bug Components: POM Reporter: Naoki Nose Attachments: plexus-utils-test-resource.tar.gz, plexus-utils.diff, src.jar The xml pull parser in plexus-utils(MXParser.java) can't handle the encoding declaration in XML declaration. So, it's impossible to use an encoding different from system default encoding. This is critical in Japan, because there is two commonly used encodings in Japanese environment(SJIS and EUC-JP). I think MXParser should handle encoding declaration in xml as described in w3c specification/ http://www.w3.org/TR/REC-xml/#sec-guessing I tried to fix this problem(see attachment). I changed the setInput(InputStream) method to detect encoding in xml declaration. For writing this code, I referred to source code of Apache Xerces. UCS-4 and UCS-2 isn't supported in this implementation, because these encoding isn't supported by Sun JDK. Xerces solves this problem by providing original reader for these encodings. I think Xerces's solution is too complex for plexus-utils. To solve this issue, it's not sufficient only to change plexus-utils, because DefaultMavenProjectBuilder reads POM by FileReader without specifying encoding. -- 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] Commented: (MNG-2148) MXParser can't handle the encoding declaration in XML declaration
[ http://jira.codehaus.org/browse/MNG-2148?page=comments#action_64002 ] Naoki Nose commented on MNG-2148: - I have attached additional two files, becaulse The format of my first attachment isn't diff format. The file plexus-utils.diff is the patch file for plexus-utils. It contains xml encoding detection code. The file plexus-utils-test-resources.tar.gz is the test resource files for MXParserTest.java. The format of these resource files is binary, so plexux-utils.diff could'nt contain these files. MXParser can't handle the encoding declaration in XML declaration -- Key: MNG-2148 URL: http://jira.codehaus.org/browse/MNG-2148 Project: Maven 2 Type: Bug Components: POM Reporter: Naoki Nose Attachments: plexus-utils-test-resource.tar.gz, plexus-utils.diff, src.jar The xml pull parser in plexus-utils(MXParser.java) can't handle the encoding declaration in XML declaration. So, it's impossible to use an encoding different from system default encoding. This is critical in Japan, because there is two commonly used encodings in Japanese environment(SJIS and EUC-JP). I think MXParser should handle encoding declaration in xml as described in w3c specification/ http://www.w3.org/TR/REC-xml/#sec-guessing I tried to fix this problem(see attachment). I changed the setInput(InputStream) method to detect encoding in xml declaration. For writing this code, I referred to source code of Apache Xerces. UCS-4 and UCS-2 isn't supported in this implementation, because these encoding isn't supported by Sun JDK. Xerces solves this problem by providing original reader for these encodings. I think Xerces's solution is too complex for plexus-utils. To solve this issue, it's not sufficient only to change plexus-utils, because DefaultMavenProjectBuilder reads POM by FileReader without specifying encoding. -- 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
