Mongo versions (many 3.6 versions right now) don't always work because versions are whitelisted in Version.java

Right now, in Version.java https://github.com/flapdoodle-oss/de.flapdoodle.embed.mongo/blob/master/src/main/java/de/flapdoodle/embed/mongo/distribution/Version.java, specific versions are called out. As new versions get introduced, they aren’t always added to this list, or even if they are, they take time to propagate through the release cycle of this repo, and then through the release cycle of other places where this plugin is used (in our case, maven central). The result is that the latest versions supported right now in the 2.0.3 version in maven central are 3.6.0 and 3.6.2. We’re trying to use 3.6.5, and the version doesn’t match exactly.

Can you change this to look for the “latest version below the number specified”? So if we use 3.6.5, it will downgrade to using the config found in the 3.6.2 version.

Right now this is manifesting itself because I can download the 3.6.5 version, but it won’t start, because it’s not grabbing the param overrides that exist in 3.6.2 in Version.java, namely the one to omit --nohttpinterface. Because of this, mongo won’t start because this option is passed, and is not allowed in 3.6.x.

[Loki-Afro]

@glajchs well if that’s all you need 😃 - done

[Loki-Afro]

@joelittlejohn so basically all he really needs is a getter on IFeatureAwareVersion which returns the Features so that one could write the follwoing:

		EnumSet<Feature> features = Version.Main.PRODUCTION.getFeatures();
		IFeatureAwareVersion iFeatureAwareVersion = Versions.withFeatures(new GenericVersion("6.6.6"), features);

that way the black magic happens not in this library. Since PRODUCTION is a moving target itself … If you wanna extend that further than check if your version starts with 3.6 and use the feaatures of de.flapdoodle.embed.mongo.distribution.Version.Main#V3_6 - features on the main versions basically never change …

@philwebb could be interested in this too

correct?