Java 7 update 45 broke local, signed TiddlySaver use, and update 25 (IIRC) broke the official, signed jar. The _45 bug is both denied by Oracle support and stated to be fixed in update 51 coming in January. I am hoping to have a signed working jar for use with 51 by the time it is released, but Oracle keeps changing the rules.
I uploaded an unsigned jar to my GitHub fork (the TiddlySaver1JarAlpha branch <https://github.com/PVHL/tiddlywiki/tree/TiddlySaver1JarAlpha/java>), but it requires changing the Java policy file as explained in another post<https://groups.google.com/forum/#!topic/tiddlywiki/kzPTzjJQA4I>. The only way I was able to save with TWC using Chrome, my unsigned jar, and update 45 was to modify my system policy file, but I use the portableApps version of Chrome on Windows 7 Enterprise, so YMMV. BTW, the only change made to the Java code was to set a flag that disabled the local directory checking code that was obsoleted. (I have had reports through another project that it is working with Chrome on a Linux install.) It didn't seem worthwhile to release a signed jar that only worked pre-update-45; I offered it if wanted, but had no takers. I can add the signed jar (renamed) to the GitHub fork if desired, but it won't work with updates 45+, and I haven't tested it with earlier Java versions yet, but it was officially signed (no time currently to wreck my Java setup and then fix it again :0). Perhaps better to wait for the next update, see if the signed jar bug is fixed, and release a working signed jar at that time if it is. Cheers, Paul. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/groups/opt_out.
