We are getting the wrong version of photonlib in simulation

[fovea1959]

We keep having the problem that somehow the wrong version of photonlib gets put on our classpath when in simulation.

This is our vendordep:

{
    "fileName": "photonlib.json",
    "name": "photonlib",
    "version": "v2024.2.6",
    "uuid": "515fe07e-bfc6-11fa-b3de-0242ac130004",
    "frcYear": "2024",
    "mavenUrls": [
        "https://maven.photonvision.org/repository/internal",
        "https://maven.photonvision.org/repository/snapshots"
    ],
    "jsonUrl": "https://maven.photonvision.org/repository/internal/org/photonvision/photonlib-json/1.0/photonlib-json-1.0.json",
    "jniDependencies": [],
    "cppDependencies": [
        {
            "groupId": "org.photonvision",
            "artifactId": "photonlib-cpp",
            "version": "v2024.2.6",
            "libName": "photonlib",
            "headerClassifier": "headers",
            "sharedLibrary": true,
            "skipInvalidPlatforms": true,
            "binaryPlatforms": [
                "windowsx86-64",
                "linuxathena",
                "linuxx86-64",
                "osxuniversal"
            ]
        },
        {
            "groupId": "org.photonvision",
            "artifactId": "photontargeting-cpp",
            "version": "v2024.2.6",
            "libName": "photontargeting",
            "headerClassifier": "headers",
            "sharedLibrary": true,
            "skipInvalidPlatforms": true,
            "binaryPlatforms": [
                "windowsx86-64",
                "linuxathena",
                "linuxx86-64",
                "osxuniversal"
            ]
        }
    ],
    "javaDependencies": [
        {
            "groupId": "org.photonvision",
            "artifactId": "photonlib-java",
            "version": "v2024.2.6"
        },
        {
            "groupId": "org.photonvision",
            "artifactId": "photontargeting-java",
            "version": "v2024.2.6"
        }
    ]
}

Somehow, if we look in the Java Properties pane in VSCode, and look under the “Project and External Dependencies” twisty, we keep seeing the 2.2 jars on the classpath.

Has anyone else seen this problem?