: Broader question is how do we work with pre-release software which is not : available on Maven Central yet, but will soon be. If the answer to that is : that we never attempt to integrate anything *before* they are released, : then that is also fine. Though, it feels limiting, if we're trying to stay : cutting edge.
cutting edge is fine for PR and patches attached to Jiras -- but I don't think anything should be committed to our repo that depends on code that isn't officially released -- not even to main. (just because our main branch contains our unstable code, doesn't mean it should contain anyone else's unstable code) Otherwise we rrun the risk of third-party code tentrails snaking into our code in ways we get more and more dependent on, and then *later* that code either changes in ways that break our compilation, or worse: changes license befroe release. These are non-problems with officially released third-party code: the *next* release might break backcompat, or change license, but the version *we* are using is always garunteed to work the same way it worked when we first started depending on it. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
