[jira] (MPIR-259) Add french localization for dependency-info
[
https://jira.codehaus.org/browse/MPIR-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312842#comment-312842
]
Guillaume Husta commented on MPIR-259:
--
Parfait merci ;-)
> Add french localization for dependency-info
> ---
>
> Key: MPIR-259
> URL: https://jira.codehaus.org/browse/MPIR-259
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependency-info
>Affects Versions: 2.6
>Reporter: Guillaume Husta
>Assignee: Stéphane Nicoll
>Priority: Minor
> Fix For: 2.7
>
>
> Please add the french localization for these properties in
> *project-info-report_fr.properties* :
> {code}
> report.dependency-info.name = Informations de d\u00e9pendance
> report.dependency-info.title = Informations de d\u00e9pendance
> report.dependency-info.description = Ce document fournit des informations sur
> la mani\u00e8re d'ajouter cette d\u00e9pendance avec diff\u00e9rents outils
> de gestion des d\u00e9pendances.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPIR-257) English localization properties misplaced (i18n)
[
https://jira.codehaus.org/browse/MPIR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=312843#comment-312843
]
Guillaume Husta commented on MPIR-257:
--
Very effective, thanks !
> English localization properties misplaced (i18n)
>
>
> Key: MPIR-257
> URL: https://jira.codehaus.org/browse/MPIR-257
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
>Affects Versions: 2.6
>Reporter: Guillaume Husta
>Assignee: Stéphane Nicoll
>Priority: Minor
> Fix For: 2.7
>
>
> These properties :
> {code}
> report.dependency-info.name = Dependency Information
> report.dependency-info.title = Dependency Information
> {code}
> should be placed in *project-info-report.properties* rather than in
> *project-info-report_en.properties*.
> As mentioned in project-info-report_en.properties, "_This bundle is
> intentionally empty because English strings are provided by the base bundle
> via the parent chain._"
> The problem is that when I generate the site with a french locale, it outputs
> "_report.dependency-info.name_" or "_report.dependency-info.title_" rather
> than "_Dependency Information_" (no french localization yet).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MPLUGIN-220) Can not use regex in @Parameter(defaultValue)
[
https://jira.codehaus.org/browse/MPLUGIN-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-220.
--
Resolution: Fixed
Fixed in [r1405658|http://svn.apache.org/viewvc?rev=1405658&view=rev]
> Can not use regex in @Parameter(defaultValue)
> -
>
> Key: MPLUGIN-220
> URL: https://jira.codehaus.org/browse/MPLUGIN-220
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
>Affects Versions: 3.0
>Reporter: Tony Chemit
>Assignee: Robert Scholte
> Fix For: 3.2
>
>
> When transform a javadoc default value
> {code}
> default-value="[a-zA-Z]{2,}-\\d+"
> {code}
> to
> {code}
> defaultValue = "[a-zA-Z]{2,}-d+"
> {code}
> I have when building :
> {code}
> Caused by: com.thoughtworks.qdox.parser.ParseException: Illegal escape
> character 'd' @[295,85] in
> file:/home/tchemit/projets/apache/maven/plugins/maven-changelog-plugin/src/main/java/org/apache/maven/plugin/changelog/ChangeLogReport.java
> at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:1018)
> at
> com.thoughtworks.qdox.parser.impl.Parser.convertString(Parser.java:1126)
> at com.thoughtworks.qdox.parser.impl.Parser.toString(Parser.java:1233)
> at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:1800)
> at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:999)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:353)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:381)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:377)
> at
> com.thoughtworks.qdox.JavaDocBuilder$2.visitFile(JavaDocBuilder.java:467)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34)
> at
> com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:464)
> at
> com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:453)
> at
> org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.discoverClasses(JavaAnnotationsMojoDescriptorExtractor.java:453)
> at
> org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.discoverClasses(JavaAnnotationsMojoDescriptorExtractor.java:443)
> at
> org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.discoverClasses(JavaAnnotationsMojoDescriptorExtractor.java:422)
> at
> org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.scanJavadoc(JavaAnnotationsMojoDescriptorExtractor.java:188)
> at
> org.apache.maven.tools.plugin.annotations.JavaAnnotationsMojoDescriptorExtractor.execute(JavaAnnotationsMojoDescriptorExtractor.java:106)
> at
> org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:108)
> at
> org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:233)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAR-161) Non default jars with classifier not attached to project
warren crossing created MJAR-161: Summary: Non default jars with classifier not attached to project Key: MJAR-161 URL: https://jira.codehaus.org/browse/MJAR-161 Project: Maven 2.x JAR Plugin Issue Type: Improvement Reporter: warren crossing Priority: Minor Attachments: maven-jar-attach-non-default.patch I wanted classifier jars to be attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-798) Commit additional files with release plugin
Thorsten Hoeger created MRELEASE-798: Summary: Commit additional files with release plugin Key: MRELEASE-798 URL: https://jira.codehaus.org/browse/MRELEASE-798 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: prepare, scm Affects Versions: 2.3.2 Reporter: Thorsten Hoeger Hi, is there any possibility to have the release-plugin commit additional files which were generated/modified in the preparationGoals. Now only the pom.xml is commited. Using scm-plugin has some serious drawbacks in this situation. If it is not possible at the moment, is there any chance to get this in the future. Maybe there could be a parameter additionalCommitFiles with a list of files to commit along with pom.xml. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-258) PrettyPrintXmlWriter encoding of \u0000 in xpp3dom attribute incorrect/different from p-u xpp3dom
Kristian Rosenvold created MSHARED-258: -- Summary: PrettyPrintXmlWriter encoding of \u in xpp3dom attribute incorrect/different from p-u xpp3dom Key: MSHARED-258 URL: https://jira.codehaus.org/browse/MSHARED-258 Project: Maven Shared Components Issue Type: Bug Components: maven-shared-utils Affects Versions: maven-shared-utils-0.1 Reporter: Kristian Rosenvold When porting surefire to m-s-u I came across the case where unicode \u gets encoded as � in an xml attribute in the prettyprintxmlwriter. This is probably the reason why the PrettyPrintXmlWriter was forked into surefire originally. Now from SUREFIRE-456 it seems like it's specification-wise illegal to do this encoding, but it does actually preserve the character value of non-printable characters. So the more I type on this issue, the more it seems like the forked PPXW actually does the best-effort "right" thing when it comes to xml encoding "any" string as long as we want to stay human readable? I need some input on this one ;) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
