Update route to compiler plug-ins

[serras]

Fixes #36

Alas, the compiler does not run in the laws and example projects (you can see this by inspecting the JAR created for laws and seeing that no @Pre or @Post annotations are present). Any ideas on how to fix this? @raulraja @i-walker @nomisRev

[serras]

But weirdly it does run in CI :/

[serras]

After digging a bit more I'm suspecting that this might be related to the versioning plug-in. In my local system I get weird versions like 2.0.2-SNAPSHOT-<date>+<time>Z, whereas in CI they are much simpler.

Is there a way to see whether this is the case? Maybe changing some configuration in the versioning plug-in? @i-walker

[JavierSegoviaCordoba]

After digging a bit more I'm suspecting that this might be related to the versioning plug-in. In my local system I get weird versions like 2.0.2-SNAPSHOT-<date>+<time>Z, whereas in CI they are much simpler.

Is there a way to see whether this is the case? Maybe changing some configuration in the versioning plug-in? @i-walker

The date you are getting is because you have something modified in local. If you commit those files you will get a specific version based on the commit hash.

[serras]

That means that I can only test the project with a clean Git status?

[i-walker]

Yes @serras, that is the case for most arrow projects if you depend on build output

[JavierSegoviaCordoba]

I can add a feature to the version plugin to force a hash version even without a clean status so we can test locally without having to commit files.

For example:

./gradlew -Psemver.useTimestamp=false

[serras]

That would be wonderful :)

[JavierSegoviaCordoba]

@serras curiously I had that property already implemented with another name and I totally forget it 😆

The usage is:

./gradlew -Psemver.checkClean=false

[serras]

It worked! @JavierSegoviaCordoba thanks for the hint :)