Set current project file when initializing the Maven resolver in the bootstrap provider

[aloubyansky]

This helps when for example dev mode is launched for a module targeted with -pl and the parent POM enables that module in a profile. Although in such a case the workspace discovery might not be including all the modules enabled in the profile. To enable all the modules, quarkus.bootstrap.effective-model-builder still has to be enabled.

This little change also may appear as a slight optimization resolving the current project path.

[famod]

Well, in a sample project I'm still seeing the same exception as in https://quarkusio.zulipchat.com/#narrow/stream/187030-users/topic/NPE.20when.20using.20quarkus.3Adev/near/268544477

Listening for transport dt_socket at address: 5005
Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException
        at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:138)
        at io.quarkus.deployment.dev.DevModeMain.main(DevModeMain.java:62)
Caused by: java.lang.NullPointerException
        at io.quarkus.deployment.dev.DevModeMain.start(DevModeMain.java:90)
        ... 1 more

I added some output right above the code you changed and I don't see it, so that part is not even invoked?

[aloubyansky]

What's your use-case @famod? It fixes what @gwenneg reported.

[famod]

I'll push a reproducer, stay tuned!

[famod]

@aloubyansky here we go: https://github.com/famod/modmono-quarkus/tree/npe-profiled-modules-dev (notice the branch)

• mvn clean install -DskipTests
• mvn -pl dist quarkus:dev

[aloubyansky]

Excellent, thanks!

[aloubyansky]

Fixed, thanks @famod !

[famod]

LGTM!