• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • None
    • Windows 7, Oracle JDK 1.7.0_79, Maven 3.2.5

      Building master branch (2.12-SNAPSHOT, a598af0) fails on Windows:

      [INFO] — maven-compiler-plugin:2.5:compile (default-compile) @ maven-plugin —
      [INFO] Compiling 77 source files to C:\Users\KAHA14\git\maven-plugin\target\classes
      [INFO] -------------------------------------------------------------
      [ERROR] COMPILATION ERROR :
      [INFO] -------------------------------------------------------------
      [ERROR] C:\Users\KAHA14\git\maven-plugin\target\generated-sources\localizer\hudson\maven\Messages.java:[17,27] error: unmappable character for encoding UTF-8
      [ERROR] C:\Users\KAHA14\git\maven-plugin\target\generated-sources\localizer\hudson\maven\Messages.java:[25,27] error: unmappable character for encoding UTF-8
      [INFO] 2 errors

      On Mac OS (same JDK and Maven level) it works just fine.

      Building v2.10 of the plugin works. I've narrowed it down to the parent upgrade from 1.554.3 to 1.580.1 triggers this failure.

          [JENKINS-29955] Can't build source on Windows

          Anders Hammar added a comment -

          Upgrading maven-localizer-plugin to v1.23 solves this. It doesn't explain the root cause though.

          Anders Hammar added a comment - Upgrading maven-localizer-plugin to v1.23 solves this. It doesn't explain the root cause though.

          Anders Hammar added a comment -

          Here's a mail thread around this issue hitting other people:
          https://groups.google.com/forum/#!topic/jenkinsci-dev/mLrAoiYH6bk

          Anders Hammar added a comment - Here's a mail thread around this issue hitting other people: https://groups.google.com/forum/#!topic/jenkinsci-dev/mLrAoiYH6bk

          Anders Hammar added a comment -

          What's the preferable way to solve this; change the troublesome unicode character or upgrade the plugin?
          The troublesome character:

          Messages.properties
          MavenVersionCallable.MavenHomeDoesntExist=Maven Home {0} doesn\u2019t exist
          

          Anders Hammar added a comment - What's the preferable way to solve this; change the troublesome unicode character or upgrade the plugin? The troublesome character: Messages.properties MavenVersionCallable.MavenHomeDoesntExist=Maven Home {0} doesn\u2019t exist

            Unassigned Unassigned
            ahammar Anders Hammar
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: