Publishing jar relies on native lib artifacts beeing
published to GH release first, thus a separate stage
is needed to guarantee order.
Signed-off-by: Alexander Bezzubov <bzz@apache.org>
Biggest benefit of using separate stage for tests and release
is that we are not waiting for osx VM instance instance any
more on every PR, just to run
`if [[ -z "$TRAVIS_TAG" ]]; then echo "Skipping this build for non-tag builds."; exit 0; fi`
there.
It alos adds clarity to CI structure => is easier to maintain.
Signed-off-by: Alexander Bezzubov <bzz@apache.org>
gimme version on TravisCI is old, 1.2 and does not support .x resulting in
`I don't have any idea what to do with '1.10.x'
but it works on latest master https://github.com/travis-ci/gimme#asking-gimme-what-a-version-is
thus opting out in always running a latest gimme
Signed-off-by: Alexander Bezzubov <bzz@apache.org>
Instead of use a command to change imports before build, using a build tag to generate the correct binary.
This will allow applications to compile enry using oniguruma with less troubles.
Signed-off-by: Antonio Jesus Navarro Perez <antnavper@gmail.com>
This change names the dependency like its called. The link to the
package was correct, but all other references were renamed where I could
find time with git grep.
Signed-off-by: Zeger-Jan van de Weg <git@zjvandeweg.nl>
