mvnd does not pick the BoM from the source tree

[ppalaga]

The $subj is just my theory to explain what just happened to me:

I added a version-less dependency apt into a Maven module camel-quarkus-platform-http-component. I also added apt properly versioned into the dependencyManagement of camel-quarkus-bom in the same source tree. Note that camel-quarkus-platform-http-component imports camel-quarkus-bom. Saved all. I am about to push the code to apache/camel-quarkus#201

mvnd clean install -DskipTests run from the top directory complained about the apt version missing in camel-quarkus-platform-http-component.

Running the same goals with the stock Maven succeeded.

So I assume the smart builder is probably not linking camel-quarkus-platform-http-component as dependent on camel-quarkus-bom.

[gnodet]

I think the problem is that something is kept in cache and not invalidated when the input has changed. I'll try to pinpoint the problem more precisely.

[gnodet]

The actual problem is that by default the maven DefaultProjectBuilder uses a ModelCache which keeps instances of org.apache.maven.model.Model in the cache. The purpose is to avoid parsing the same pom multiple times in a reactor, but it does not take into account the fact that the local projects may have changed.

[ppalaga]

What would be the best workaround? To kill the daemon? Or maybe there is a switch to restart the daemon?

[gnodet]

I'm working on implementing a ProjectBuilder with a cache that will fix the problem.