I’m working on improving the CI/CD for Orekit. One of the most annoying issue is that the
develop branch of Orekit regularly depends on a SNAPSHOT version of Hipparchus. Currently, the CI/CD is based on feature/issue of Jenkins, allowing to share a
.m2 between multiple jobs from distinct projects… An other side effect (from my external point of view): any new contributor to Orekit has to download and build Hipparchus also, while she is not necessarily interested on.
The ideal solution would be to prohibit such situation and systematically publish a RELEASE of Hipparchus before upgrading Orekit’s dependencies. Of course, ideal is not the most simple to do and can bring more complex situations in the development process.
The other solutions are to publish these SNAPSHOTs somewhere.
As far as I know, the maven central do not let us publish SNAPSHOT.
I then though about Github Packages feature as Hipparchus’ source code is hosted there, but same rule: no SNAPSHOT hosted.
So, the only remaining solution seems to be to host these SNAPSHOTs on the (new) Nexus instance for Orekit. One side effect: I fear that I will need to expose this dependency directly inside the
pom.xml (not able to hide it somewhere else).
Is it acceptable to have Hipparchus project depends on Orekit’s resources?