Short term solution to always re-resolving

This change is a short term solution to the always re-resolving problem fixed by !12 (merged).

This is because I'd like to release a v2.2.6 with this fix (and a small improvement to the logging setup). A more substantial change will be made later on (on master, rather than the 2.2.x release branch).

added 1 commit

• 2541f1fb - Ensure that the resolver is defined before the is installed check. Only...

Compare with previous version

@mihostet - just to let you know that I'd like to release this change (without all of the error propagation changes I proposed previously) as v2.2.5.

The work on master currently shall be known as v3 and will include the Jpype update. I'll maintain a v2.2.x branch until we have got v3 ready to ship.

added 1 commit

• c4e6569a - Ensure that the resolver is defined before the is installed check. Only...

Compare with previous version

added 1 commit

• 75ce7500 - Ensure that the resolver is defined before the is installed check. Only...

Compare with previous version

OK for me.

approved this merge request

added 1 commit

• fbc77166 - Update the version to v2.2.5.

Compare with previous version

closed

mentioned in merge request !40 (closed)