Forum Discussion

rpatrick00's avatar
rpatrick00
Contributor
6 years ago

Maven archetype build errors

It seems that the 4.22 archetype is generating code that is failing its own generated unit tests… ☹️ d:\src\snaplogic-poc\snap-dev\odyssey-api-snappack>mvn clean verify [INFO] Scanning for projec...
ptaylor's avatar
ptaylor
Employee
6 years ago

Hi @rpatrick00. I’m testing the 4.22 archetype right now and those failures are not happening on my system. Note that the stack traces in the output should happen, but those tests are designed to expect those errors, so they should succeed. I’m wondering if this is could be a Windows issue. I’ve been testing on a Mac. Let me take a closer look to see if I can spot what’s happening. Stay tuned.

  • ptaylor's avatar
    ptaylor
    Employee
    6 years ago

    What version of java are you using?

    • rpatrick00's avatar
      rpatrick00
      Contributor
      6 years ago
      d:\src\snaplogic-poc\snap-dev\odyssey-api-snappack>java -version
openjdk version "1.8.0_212"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_212-b03)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.212-b03, mixed mode)
      • ptaylor's avatar
        ptaylor
        Employee
        6 years ago

        My first instinct was right. It’s a Windows vs Mac thing. Line endings! It’s right there in your output:

        org.junit.ComparisonFailure: expected:<…valid count value -2"
        } ]
        }> but was:<…valid count value -2[\r]"
        } ]
        }>