Closed obfischer closed 10 years ago
This indicates that data of an older jQA /Neo4j version is still present in the workspace. After executing mvn: clean the problem should be gone. Nevertheless automatic store upgrades shall be activated by default to allow incremental scanning in the future, will be implemented.
From an enduser perspective this is annoying as you can't see a simple solution in the first moment. The hint with the configuration parameter is even more confusing.
Maybe it would be enough for the first time to catch this error and to add a hint to the output the run mvn clean
.
Committed a fix for 1.0.0-RC.
Thank you. I will test it.
Works. First I build with Milestone 3 and afterwards mit 1.0.0-RC-SNAPSHOT. Store were automatically updated.
After upgrading my Maven Plugin Dependency to 1.0.0-M4 the build fails with the following message: