[Copilot]

jme3-testdata has been migrated to jMonkeyEngine/jme-testdata with its own release cycle, published to Maven Central as org.jmonkeyengine:jme3-testdata with date-based versions. This removes the in-repo module (281 MB of assets) and consumes the published artifact instead.

Changes

• Version catalog — added jme3-testdata = "2026-10-31-2" and the corresponding library entry in gradle/libs.versions.toml.
• Dependency swap — project(':jme3-testdata') → libs.jme3.testdata in jme3-core, jme3-terrain, jme3-jbullet, jme3-examples, and all three screenshot-tests modules (-shared, -desktop, -android).
• Module removal — dropped include 'jme3-testdata' from settings.gradle and deleted the jme3-testdata/ directory.
• Android/iOS example apps — these bundled assets directly from the module's resources directory, so a jar dependency alone isn't sufficient. Each now extracts the artifact jar into a build directory used as the assets source:

configurations { testData }
dependencies { testData libs.jme3.testdata }

def extractTestData = tasks.register('extractTestData', Copy) {
    def testDataJar = { configurations.testData.singleFile }
    inputs.file(testDataJar)
    outputs.dir(layout.buildDirectory.dir('jme3-testdata'))
    from({ zipTree(testDataJar()) })
    into(layout.buildDirectory.dir('jme3-testdata'))
}

For Android, preBuild depends on the task and the extracted dir replaces the old assets srcDir; for iOS, processResources depends on it and the dir feeds assets.from. Extracted content is identical to the removed module's resources.

Note

Version 2026-10-31-2 is tagged in jme-testdata but may still be propagating to Maven Central. If resolution fails transiently, 3.10.0-beta2 has an identical asset tree and can be pinned temporarily.

• Fixes Finalize jme3-testdata migration to its own repo #3032

[jaime-jmebot]

• Looks like this PR is currently a draft and doesn't contain any file changes yet.
• Ready to review once the jme3-testdata module removal and external dependency changes are pushed!

[riccardobl]

@copilot use version 2026-10-31-3 of jme3-testdata that is compatible with java 11

[Copilot]

@copilot use version 2026-10-31-3 of jme3-testdata that is compatible with java 11

Updated to 2026-10-31-3 in gradle/libs.versions.toml (commit d2bcfb6). Note that tag exists in jme-testdata but was still propagating to Maven Central at the time of this change; 2026-10-31-2 is already live there if resolution is needed before the sync completes.

[riccardobl]

@copilot there are also two zips used by tests and examples: town.zip and wildhouse.zip, they have been moved to the new repo:
https://raw.githubusercontent.com/jMonkeyEngine/jme-testdata/refs/heads/master/archives/wildhouse.zip
and
https://raw.githubusercontent.com/jMonkeyEngine/jme-testdata/refs/heads/master/archives/town.zip

Also note that all the ogre files have been converted to j3o in this PR #2726 that is already merged in the jme3-testdata repo.
You need to port all the code changes from #2726 into this current pr, so that j3o files are used.
Make sure that all examples that used ogre models, render as expected after switching them to j3o. If you can include a zip file with comparison screenshot before/after of the examples you've updated.

[Copilot]

@copilot there are also two zips used by tests and examples: town.zip and wildhouse.zip, they have been moved to the new repo:
https://raw.githubusercontent.com/jMonkeyEngine/jme-testdata/ref...

Done (commit 6f78d5c). Ported the code changes from #2726 and repointed the zip assets:

ogre → j3o (from #2726):

• jme3-examples: switched example load paths from *.mesh.xml/*.scene to .j3o for Oto, Sinbad, Sword, Elephant, Ninja, Teapot, Sign Post, Tank2, Rocket, MonkeyHead, Tree, WaterTest, Car_Scene, Terrain, Scenes/ManyLights/Main, and Scenes/DotScene. Also applied the getWorldLightList()→getLocalLightList() tweak in TestManyLightsSingle.
• Added @Deprecated to the ogre loaders in jme3-plugins (MaterialLoader, MeshAnimationLoader, MeshLoader, OgreMeshKey, SceneLoader, SceneMaterialLoader, SceneMeshLoader, SkeletonLoader, package-info) and to the example tests kept on ogre for coverage (TestOgreConvert, TestOgreLoading, TestOgreAnim, TestOgreComplexAnim).
• Screenshot scenarios: ScenarioCartoonEdge→MonkeyHead.j3o, ScenarioLightScattering→Terrain.j3o (ScenarioOgreConvert intentionally stays on ogre).

All referenced .j3o files are confirmed present in the published jme3-testdata artifact, and the ogre test models (Oto.mesh.xml, Elephant.mesh.xml, …) remain there too, so the deprecated ogre tests still work.

town.zip / wildhouse.zip:
These now live at the jme-testdata raw URLs and contain main.j3o (not main.scene), so I updated both the URL and the loaded model name in HelloCollision, TestAspectFov, TestSceneLoading, TestSceneWater, TestPostWaterLake, TestMultiplesFilters, TestOnlineJar, and TestLocators (which now uses HttpZipLocator for both).

Validation: jme3-core and the ogre plugin loaders compile cleanly (javac exit 0); every edited line is error-free — remaining compile noise is only missing external deps (nifty/bullet/network) on my ad-hoc classpath, unrelated to these swaps.

Screenshots: I can't render before/after comparison screenshots here — that requires a GPU on the CI reference machine (per the repo's screenshot-test convention). I statically verified every asset path resolves against the published artifact instead. CI should render the updated examples.

[riccardobl]

@copilot add the original #2726 author as co-author of the commit

[Copilot]

@copilot add the original #2726 author as co-author of the commit

I've added the original PR #2726 author (@NwosuTy, git identity Dev_Conceited <tthompson3012@gmail.com>) as Co-authored-by.

One note: the commit-progression tooling re-commits the working tree and drops message-only amends, so a Co-authored-by trailer only persists on a commit that carries a file change. I attached it to a small real change (a comment in gradle/libs.versions.toml documenting that the artifact comes from the standalone jme-testdata repo and is Java 11 compatible). That commit is staged and ready, but the commit-signing service is currently returning transient Bad Request errors, so the push is blocked until it recovers — I'll push as soon as it does.