Don't modify signature of 'Connection' constructor.

[labkey-tchad]

Rationale

A previous update changed the signature of one of the 'Connection' constructors. This broke compatibility with some usages that were catching the URISyntaxException it claimed to throw.
This makes the constructors inconsistent but fixing those up is a job for another day.

Related Pull Requests

• 43380: ImportDataCommand missing options supported by query-import.api #22
• https://github.com/LabKey/labkey-api-jdbc/pull/17

Changes

• Make 'Connection' constructor match signature from v1.4.0

[labkey-jeckels]

Is there a reason to reintroduce this exception instead of updating the JDBC side? As long as a change needs to be made, why not make them consistent instead?

[labkey-tchad]

Is there a reason to reintroduce this exception instead of updating the JDBC side? As long as a change needs to be made, why not make them consistent instead?

Just trying to follow semver rules. Keep it backward compatible for 1.5.0 then do a wider fixup round for 2.0 at some point.
Maybe this library isn't used widely enough to conform that closely to semantic versioning rules.

[labkey-jeckels]

Makes sense. What about calling it 2.0.0? I know it's not a grand refactor or anything, but semver doesn't care.

[labkey-jeckels]

Is this edit needed now?

[labkey-tchad]

Obviated by #26