Uploaded image for project: 'Maven Plugin Tools'
  1. Maven Plugin Tools
  2. MPLUGIN-101

Allow customization of file encoding used for mojo extraction

    XMLWordPrintableJSON

Details

    • Patch

    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.

      Attachments

        1. source-file-encoding.patch
          17 kB
          Benjamin Bentmann

        Issue Links

          depends upon

          Task - A task that needs to be done. MPLUGIN-110 Make easier to pass parameters into MojoDescriptorExtractors

          • Major - Major loss of function.
          • Closed
          is depended upon by

          Improvement - An improvement or enhancement to an existing feature or task. MPLUGIN-111 Warn about usage of platform encoding

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. MNG-2216 Add default encodings section to POM

          • Major - Major loss of function.
          • Closed
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. MPLUGIN-100 Allow customization of file encoding used for generated help goal

          • Major - Major loss of function.
          • Closed

          Activity

            People

              jdcasey John Dennis Casey
              bentmann Benjamin Bentmann
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: