Publishing with multi reobfuscate

[Icosider]

If you use multi reobfuscate, only the result of the last one will be sent when publishing. This approach is not always convenient. In the case of shadowJar, this is an ideal and convenient approach, but if the mod has a split system into a client and a server, then several options are expected for publication:

1. The client and server builds will be published, as well as the source code.
2. Publishing universal jar only (aka default gradle task)

Possible solutions:

1. Do not overwrite(clear?) components.java
2. Add additional components designed specifically for publishing reobfuscated jar files.

[Technici4n]

It's quite weird that we clear the artifacts like this:
https://github.com/neoforged/ModDevGradle/blob/main/src/legacy/java/net/neoforged/moddevgradle/legacyforge/dsl/ObfuscationExtension.java#L135

I don't think that we clear the components, however maybe clearing the artifacts is enough to prevent the previous variants from being published?

[Icosider]

I tried this option and it looked quite uncomfortable, because just a point is not enough. It is necessary to "return" the artifact that mdg cleared.

[neoforged-releases]

🚀 This issue has been resolved in ModDevGradle version 2.0.89, as part of #256.