Upgrading bundled Nifty about sdk HOT 7 CLOSED

Not exactly sure how you can upgrade nifty for the SDK without updating it for the engine.
In any case, we should not use snapshot versions of nifty gui. Perhaps it is better to wait for 1.4.2 to be released.

from sdk.

Well I was thinking that Nifty is treated as an external library (since it's maven repo is in the build.gradle), so my guess was it's jar is simply packaged and used.

On the other hand I guess nifty has some jme-specific code which seems to reside in the engine.
Anyway if you look into the issue on nifty-gui/nifty-gui#364 void256 says that he see's no problem with using SNAPSHOT in JME (but of course it's up to you to decide)

from sdk.

... yes, as outlined in this comment: nifty-gui/nifty-gui#364 (comment) and under certain restrictions explained in that comment ONLY. And not in general! Of course it's always best to use a released version!

We've been here before and we don't want to delay any JME-release waiting for a Nifty release since chances are that both usually don't align.

from sdk.

1.4.2 is out for about a year and a half now. Where will we update it? In the sdk or in the engine? Or we just continue using current version since not a lot of people use nifty anyway?

from sdk.

The engine would have to update it's dependencies. I'm guessing here but I guess the Nifty dependency the SDK has is only the Nifty Visual Editor and jme3-nifty-gui will pull in the appropriate nifty version itself.

from sdk.

JME 3.1.0-stable had Nifty 1.4.2 in it, as does 3.2.0-stable.

from sdk.

corelibs dep("org.jmonkeyengine:jme3-niftygui:$jmeEngineVersion", true, true) -> we depend on Nifty via the engine, nothing more, so this issue is solved.
Plus: The Engine already uses 1.4.2, so jMonkeyEngine/jmonkeyengine#330 is also solved.

from sdk.