Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NullPointerException when starting with quarkus:dev goal #828

Closed
sobkowiak opened this issue Mar 1, 2020 · 2 comments
Closed

NullPointerException when starting with quarkus:dev goal #828

sobkowiak opened this issue Mar 1, 2020 · 2 comments
Milestone

Comments

@sobkowiak
Copy link
Member

I have checked out the 1.0.0-M3 tag and tried to start the timer-log sample using mvn clean compile quarkus:dev. The result is

Listening for transport dt_socket at address: 5005
Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException
        at io.quarkus.dev.DevModeMain.main(DevModeMain.java:71)
Caused by: java.lang.NullPointerException
        at sun.nio.fs.UnixPath.normalizeAndCheck(UnixPath.java:77)
        at sun.nio.fs.UnixPath.<init>(UnixPath.java:71)
        at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281)
        at java.nio.file.Paths.get(Paths.java:84)
        at io.quarkus.dev.RuntimeUpdatesProcessor.checkForFileChange(RuntimeUpdatesProcessor.java:307)
        at io.quarkus.dev.DevModeMain.start(DevModeMain.java:91)
        at io.quarkus.dev.DevModeMain.main(DevModeMain.java:67)

The same with previous versions. I tried also hello world created from scratch (without Camel) and it works (with the same Quarkus version)

My Java and Maven versions

mvn -v
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T21:00:29+02:00)
Maven home: /home/ksobkowiak/.sdkman/candidates/maven/current
Java version: 1.8.0_242, vendor: Oracle Corporation, runtime: /home/ksobkowiak/work/ttseiii/soft-knative/jvm/graalvm-ce-java8-20.0.0/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "5.5.5-200.fc31.x86_64", arch: "amd64", family: "unix"
@aldettinger
Copy link
Contributor

Thanks for taking a look @sobkowiak, I've checked the 1.0.0-M3 tags but I'm not able to reproduce this issue. Could you please check the same against 1.0.0-M5 (it's quarkus 1.3.0.Final under the hood).

Also, the quarkus issue #6168 looks very similar, could you please try the provided reproducer to check whether you would be hitting this issue.

@ppalaga
Copy link
Contributor

ppalaga commented Jun 10, 2020

This happens when an example is run unchanged inside the Camel Quarkus source tree. You need to do one of the following:

(a) use mvn clean compile quarkus:dev -DnoDeps instead of mvn clean compile quarkus:dev or

(b) replace <artifactId>camel-quarkus-build-parent</artifactId> in the example's pom.xml with <artifactId>camel-quarkus-bom</artifactId>.

The option (b) is documented in https://camel.apache.org/camel-quarkus/latest/user-guide/first-steps.html Thus closing as not a bug.

@ppalaga ppalaga closed this as completed Jun 10, 2020
@ppalaga ppalaga added this to the 1.0.0-CR3 milestone Jul 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants