Configure PublishingExtension for WorldEdit Sponge (#2761)
Currently, sponge api aren't be published to the maven repository (only the `pom`s are): https://maven.enginehub.org/repo/com/sk89q/worldedit/worldedit-sponge/7.4.0-SNAPSHOT/
Looks like the `worldedit-sponge` is just not configuring publishing:
- Sponge (No `configure<PublishingExtension> `) - https://github.com/EngineHub/WorldEdit/blob/version/7.3.x/worldedit-sponge/build.gradle.kts
- Bukkit (configures it) - https://github.com/EngineHub/WorldEdit/blob/version/7.3.x/worldedit-bukkit/build.gradle.kts#L110
- Fabric (configures it) - https://github.com/EngineHub/WorldEdit/blob/version/7.3.x/worldedit-fabric/build.gradle.kts#L71
Presumably since `worldedit-sponge` is missing:
```kt
configure<PublishingExtension> {
publications.named<MavenPublication>("maven") {
from(components["java"])
}
}
```
It doesn't get the information from the `java-library` plugin to actually include the jar, so it just includes the pom.
Unfortunately I obviously don't have permission to publish the enginehub repository, but perhaps someone could take a look to see if this fix would work? (dece49b5 by tyhdefu)
Update click and hover text component serialization for 1.21.5. (#2757)
Hacky workaround by overwriting the text3 StyleSerializer class with our own modified copy.
Note that the hover events "show_entity" and "show_item" aren't supported as they no longer take a rendered component, but just the NBT structure.
Behavior remains unchanged if 1.21.4- is detected.
Fixes #2756. (ce043859 by wizjany)
Do not paste unsaveable entities in their default state (#2721)
Remove a redundant passenger check, as entity.save() returns false in that case.
This also causes leash knots to not be copied. I don't think this is a problem because:
- They would not be saved to disk, it's misleading for users that they appear.
- Pasted leashed mobs still think they're leashed to the original position and get unleashed* - no change in behaviour.
\* Unless they're pasted close enough to the original position, in which case this has better behaviour because they create their own leash_knot entity. (25988878 by brickmonster)
