Affects Version/s: None
Fix Version/s: BLAZEGRAPH_2_0_0
BLZG-37 is a dependency problem. Once we document how the generated artifacts are to be published and resolved I can resolve that ticket.
*Current Policy: *
The development branches all specify the version as follows. This assumes that we are in the development process leading up to a 1.5.2 release, which is currently true. With this setting made consistently in the pom for each bigdata/blazegraph module the modules will build from mutually consistent snapshots.
General Policy: TBD
We need a more general policy that will allow us to run maven CI builds on branches without causing interactions with the maven CI builds on master.
When changing versions
Changing versions can get the CI builds out of whack, especially if some of the CI jobs have tests that fail (since in this case they will not deploy their artifact and downstream projects can not succeed). The following incantation can be used to force deployment of the snapshot artifacts so the CI build can succeed: