Building with Maven 3.6.3 about evomaster

[arcuri82]

thanks for reporting this issue.

I have not seen it before, and I cannot reproduce it. So, I ll need some more info to investigate it:

• output of java -version
• output of mvn --version
• name of the project in EMB you are trying out
• terminal command-line you are using to run evomaster.jar
• does the same problem appear if you use evomaster.jar version 1.0.2 (downloaded from GitHub) instead of locally built 1.0.2-SNAPSHOT?

[bruceyy]

mvn --version
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_252, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-40-generic", arch: "amd64", family: "unix"

java -version
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-8u252-b09-1ubuntu1-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)

I have tried scout-api and features-service.

running java -jar core/target/evomaster.jar

I have downloaded the v1.0.1 jar and that works, whereas my locally built 1.0.1 throws the same error as above.

thanks

[arcuri82]

hmmm... that is really weird. Usually, that error message would be present when Jackson support is not provided to Jersey. But that is explicitly done in the pom file with:

            <dependency>
                <groupId>org.glassfish.jersey.media</groupId>
                <artifactId>jersey-media-json-jackson</artifactId>
                <version>${jersey.version}</version>
            </dependency>

can you check if those files end up in the generated jar? eg.:

cd core/target/
unzip evomaster.jar -d foo
ls foo/org/glassfish/jersey/jackson/

furthermore, which mvn command did you use when building locally?

thanks

[arcuri82]

might also be worthy to delete the files from:
~/.m2/repository/org/glassfish/jersey/media/
to force Maven to re-download them (in case there was some file corruption issue there...)

[bruceyy]

Yup files are in the generated jar

Command used : mvn clean install -DskipTests

I have wiped my maven local repo and still getting the error

[bruceyy]

I have managed to build from source v1.0.1 on a different machine and copy it over, run it, and its working (woohoo).

It would seem there is something quirky going during the compilation process - thanks for your help and I will update the issue if i find out exactly what it was causing the error

[arcuri82]

thanks for the update.

wondering if it is something related to the version of Maven... you wrote you used 3.6.3, whereas on my machine I still have an older 3.5.0

What is the Maven version in the other machine you managed to successfully build?

[bruceyy]

yeah you got it - switched to maven version 3.5.0 and can successfully build and run v1.0.1 :)

(other machine was version 3.3.9)

[arcuri82]

thanks for checking this out.
i ll need to look into why it fails with 3.6.3

[arcuri82]

updating maven-assembly plugin seems to fix the issue