IMHO the language exposed here is not suitable to
push forward our JInput integration here.
Note that 'can somebody please' is a quite aggressive & desperate request.
To give a quick answer: No, I don't sign anything w/o at least a very brief
review. Especially I don't perform services by [almost] yelling at me :)
Please understand that we all have different priorities,
However, migrating JInput will be done as said, I may even be able to
perform this task this weekend - before looking at Java3D .. then OSX .. etc.
(Mind: You didn't offered your time to perform this task)
Right now .. other fixes are on it's way.
Please send me the email address of 'Endolf' in private, thank you.
I will clone the SVN repository to a GIT repository,
since I don't believe SVN is suitable for our cause and
actually I have bad experiences w/ the SVN merging capabilities.
- It should be OK for 'Endolf' to merge our changes back if so desired.
- It is OK for us to merge 'Endolf's ongoing changes, so we can be assured
we stay on top of his.
After this is done, including the native library loading patch,
I will add JInput to our jenkins build and produce a new release.
Sunday if lucky, otherwise within next week.
> Also, Endolf has been working really hard on this stuff. It's a shame they are
> not even signed (valid certificate).
Why blaming somebody of something, which is not in his interest ?
> Additionally, when signing these jars make sure you remove Endolf's
> certificate from the jars otherwise an Expired Certificate error will be
> thrown when executed. You know, the usual procedure.
We will only sign our own builds and .. see above.