Closed rdeltour closed 9 years ago
Strange. Yes liblouis-java 1.3.0 is not in central yet, but it is staged, and it worked fine on Travis.
Yes, master is not a child of v1.9. I thought this wouldn't be a problem because you have the same situations when you do release branches. Yes, merging the release branch to master is what I had in mind too (if you want to delete the release branch and be sure it is not garbage collected).
liblouis-java 1.3.0 is not in central yet, but it is staged, and it worked fine on Travis.
Oh, that's it then. The staging repo is enabled on Travis, but may not be on users' setup (e.g. it's not enabled on mine at the moment). It's a bit dangerous that Travis enables repos that users may not have, but otherwise we would have to release to Maven Central sequentially, not many staged projects as a bulk, otherwise Travis wouldn't find the yet-unreleased-to-central projects.
I have released liblouis-java 1.3.0. You want me to do the 1.9 merge?
The
master
branch is not a child of therelease/v1.9
tag, we need to clean this up, maybe just merge the branch containing the release to the master.Also, when building the
master
branch, I get an error:It seems Maven Central contains
org.liblouis:liblouis-jar:1.2.0
but not1.3.0
. @bertfrees can you look into it?