Problems with "mvn clean install"

[chrisdutz]

Hi,

I don't think it will be easy to fix this, but I wanted to documet it for the future.

We use JQA 1.1.3-SNAPSHOT in conjunction with the insanely cool useExecutionRootAsProjectRoot option set to true. This works as it should.

Now we had the problem that in one project we could do "mvn clean install" and in another we couldn't. Yesterday I found out what was different. In the working version the reactor root was a parent of the child modules and in the not-working version it wasn't. It seems Maven would usually build the pom artifact at the end, unless it is referenced by another module (the parent dependency).

In the working case the reactor root is referenced by the children and the "clean" is done first. If the root is not referenced by any other module, it is processed at the end and hereby the clean is done at the end. On windows machines this will fail as the Neo4j system has locked the data files. On a Mac it will simply delete them and after the build the data is lost.

Chris

@ascheman