Refactor labkey-api-java repository

[labkey-adam]

Rationale

The extra labkey-client-api folder in this repository is unnecessary, left over from when the repo used to house labkey-api-sas as well.

Related Pull Requests

• Remove SAS macros and wrapper classes from Java 17 version of remoteapi #34

Changes

• Eliminate unnecessary intermediate folder

[labkey-adam]

@labkey-tchad I think I'll need your help to get the Java Remote API suite to run after this refactor

[labkey-susanh]

For better or for worse, we currently publish this under org.labkey.api/labkey-client-api This will no longer be the case by default with this move. We'll need to either update the repository name to be labkey-client-api or change the name in build.gradle file.

[labkey-susanh]

We're going to need a new gradle plugin release for this change. We have a method there called getRemoteApiProjectPath that is used for declaring dependencies in various places

[labkey-tchad]

For better or for worse, we currently publish this under org.labkey.api/labkey-client-api This will no longer be the case by default with this move. We'll need to either update the repository name to be labkey-client-api or change the name in build.gradle file.

Whatever the name we chose, we can't rely on the repository name to define it. TeamCity uses some internal logic to name the root directory for builds. This causes gradle to produce some real nonsense names:

@labkey-adam The solution is to define the name in settings.gradle

rootProject.name='labkey-client-api' # or 'labkey-api-java'

[labkey-adam]

@labkey-tchad of course, 77414112b699049a... not sure why I couldn't find my artifact. :) https://labkey.jfrog.io/ui/packages/gav:%2F%2Forg.labkey.api:77414112b699049a?name=77414112b699049a&type=packages