On 03/04/12 19:57, Matthew Toseland wrote: > Nextgens is convinced that many of the problems users have installing on > Windows are due to firewalls blocking the localhost connection between the > wrapper binary and the JVM running Freenet. The usual solution proposed is > to split up freenet-ext.jar, which infinity0 has been working on. Can we do > a quick fix though? Just introduce the new wrapper jar on the classpath in > new installs, so that it overrides the wrapper classes in freenet-ext.jar? > The main difficulty appears to be update.cmd - on Windows, it will clobber > wrapper.conf in some circumstances, in which case it could revert it to a > version without the new wrapper.jar and thus break it. > > See bug: https://bugs.freenetproject.org/view.php?id=4075 >
How does splitting up freenet-ext.jar help with "not creating a localhost socket"? i.e. can you explain the solution in more detail. -- GPG: 4096R/5FBBDBCE https://github.com/infinity0 https://bitbucket.org/infinity0 https://launchpad.net/~infinity0 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20120403/14739788/attachment.pgp>
