Jinput->Controller.jar?

Engines, Libraries and Tools JInput
#21

Hi
I commit a change the main build script that copies a few files across to a dist dir and zips them up, it leaves the originals where they were (bin, lib and src/tests/controller), as/when this automated nightly build thing happens it can easily be removed, it effects no other target (except clean, easy to remove again). Is it ok to leave it in for now?

Cheers

Endolf

P.S. the plugin has never ended up under bin or lib, it’s always been under src/tests/controller, from what your saying this is a mistake as it should be under bin or lib, correct?

#22

[quote]Hi
I commit a change the main build script that copies a few files across to a dist dir and zips them up, it leaves the originals where they were (bin, lib and src/tests/controller),
[/quote]
Cool thats fine for now :slight_smile:
Thanks

Um yeah sure sounds like it but i find it hard to believe. Are you SURE there isn’t a jar file being built and copied to the appropriate bin or lib under the plug-in branch? (Ill check it on monday but i’d be astounded if this slipped through.)

JK

#23

The coreAPI gets copied down into the plugins directory but I believe endolf is saying that the plugin .jars and natives don’t end up in the /bin or /lib directories of jinput itself.

#24

[quote]I appreciate your enthusiasm but I kinda need to leave the build target directories as they were as thats a standard that was agreed on for all the “core” APIs and i don’t want to get out of synch with them. Also, the folks working behind the scenes on things like the automated build systems expect this uniformity.

Thanks

JK
[/quote]
Can we get a document that shows the expected directory layout of the core projects? (If it exists in CVS and I’ve missed it, just clue me in.)
If something was agreed on it should be documented.