The wrapper enables us to update the node. We do this by alternating between freenet.jar and freenet.jar.new.
On Sat, Feb 10, 2007 at 09:35:45PM +0100, bbackde at googlemail.com wrote: > I just experienced a phenomenon that I don't understand. > > I run the node on a WinXP box and use the wrapper. There is a > freenet.jar in the node directory. The node was 1012. Then I updated > SVN and got the source for 1014. I added some code changes that send a > new message if the priority of a persistent request changes. I built a > freenet.jar and replaced the freenet.jar in the node directory, and > started the node. > Surprise: the displayed node version was still 1012, without @custom@! > My new message was not sent, so this seemed to be a true, unchanged > 1012. After trying this and that, I updated the node using update.cmd > (there was still no update message from the node). I started the node > and it showed 1014, as expected. Then, I replaced the freenet.jar with > my own version (same freenet.jar as before) and started the node. > Voila, the version was 1014 @custom@ and my own fcp message was > sent!!! > > So what happened there? What magic does the wrapper do, where did it > get the 1012 from when I replaced the freenet.jar with 1014 @custom@? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20070210/2bc2fbd5/attachment.pgp>
