Mechanize Keeping Ion Java Pinned to Fusion Java's Dependency Version

[SharkBaitDLS]

Right now, we're hard-coding the version of Ion Java we pull from Maven. We should come up with a mechanism to get the dependent version of Fusion Java instead.

Note, this may just end up being a solved problem once Fusion Java is in Maven -- we may be able to just use the CLI to retrieve a specific Fusion Java version + its specific dependency.

[toddjonker]

If we want to source jars from Maven, we're probably going to want to run dependency resolution. Might be easier to take the artifacts from the SDK build, or something.

[SharkBaitDLS]

The SDK build approach may work too -- the main thing I want is to work towards a solution where we pull fusion-java and its dependencies as a single closure. I was considering just outright having a pom.xml file and letting Maven do it, but that I think locks us out of having multiple versions available at once to run should we want to go that route.