I am far from being a Maven expert so maybe there is a good way to do what you want here, but generally I avoid trying to run Maven for some submodules only.
So instead of `mvn test -f extensions/geojson` I would just run `mvn test`… That would run tests on all other modules but perhaps it's not such a big deal? Backend tests are relatively quick.
The proper solution, I think, would be that you don't even have to clone OpenRefine's repository to work on your own extension: you should be able to do it independently, in your own Maven project. For that, I am planning to publish Maven artifacts for OpenRefine's modules: https://github.com/OpenRefine/OpenRefine/issues/2254
But as long as our artifacts are not published on Maven, your
approach seems to be the easiest way to go.
You received this message because you are subscribed to the Google Groups "OpenRefine Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrefine-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/a20b2cff-3a32-42ff-be9e-299e9feb54a6n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openrefine-dev/c8f03a28-e5eb-406e-bf5b-2b72721ef213n%40googlegroups.com.