At present, I'm not likely to accept a PR as a result. PRs, although welcome and invited, might be based on the repo as it existed some time before, and I will have taken the code in a new direction as I figure out things. Time is on our side, 1.13 is the earliest this will land, and that is some time away yet. This code is often sitting on my desktop in a half working state as I take time to work on it. With Java9 ripping the rug out of how everything is supposed to work, having a broad test suite that represents "yup, it works" will be invaluable. I hate how unreproducible legacylauncher is. I want everything to have a test, if possible. we probably still need to do the signed but not signed jar hacks from legacylauncher.there is probably a third "initialization cycle" in the launcherservice that isn't represented yet - for once the classloader has stood up.If we die, I want a log file to tell us why immediately, no speculations. Having it baked right into the basic framework removes a huge burden from a lot of places.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |