Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: really odd problem with jar signing Date: Sun, 13 Jan 2013 20:08:54 -0800 Organization: Canadian Mind Products Lines: 23 Message-ID: References: <2o21f8p1fem5ghqimkgogvg8lrdvk9lcgr@4ax.com> <5j31f85qbc4juk3a62sft33pjn39gcd66n@4ax.com> Reply-To: Roedy Green NNTP-Posting-Host: K2Qzzs3EAqXk5RLzfhxcSw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: csiph.com comp.lang.java.programmer:21394 On Sun, 13 Jan 2013 16:44:55 +0000 (UTC), Andreas Leitgeb wrote, quoted or indirectly quoted someone who said : >Thanks to all participating so far! I would certainly help to have a look. I hope my ideas did not trigger too much of a goose chase. There is the old reliable technique. What did I change just before it stopped working?. The chain of causality may be bizarre, but that is where to look. Try putting it back the way it was until the problem goes away, then incrementally change and test till you out precisely what triggers the failure. With that in hand, others may be of more help. Murphy could be after you. The digest comes out 0. :-) -- Roedy Green Canadian Mind Products http://mindprod.com The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time. ~ Tom Cargill Ninety-ninety Law