Your InterMine data parser has a version.
The version for your mine's custom source is the
version value in the
build.gradle file in your sources directory. When you install your source, the JAR of the correct version will be created.
See FlyMine's build.gradle file.
We recommend you use semantic versioning.
To use a specific version, add a parameter to your project XML entry.
You will get an error if it can't find a JAR with this version. Note that this is a simple string comparison, e.g. "2.0" will NOT match with "2.0.0".
If no version is provided, the default InterMine version is used. For InterMine's bio sources, a global variable is set in the
gradle.properties file in your mine.
Here is an example error:
Maven is looking in your repo and Maven central for your JAR as version 4.0.0. You have two choices:
- Update the version of your source to be 4.0.0.
- Update your project XML to set the version to look for to 4.0.0.
See the above sections for how to do this.
Here is an error when Maven can't find your JAR:
You can see that Maven first looking in your local Maven repo, then it looked in the remote Maven repository.
This is because in the gradle file, we have specified which repositories to search. Maven will search in order. It will search the first repo for the specified JAR. If it fails, then it will continue to the next repository.