to do the first time that I noticed I added these files with those unneccesry
  attributes.
* Set the "manual merge" attribute on these files.

working directory set to $INSTALL_DIR, C:\Program Files\I2P is not removed in
XP.

...but even with the working directory removed, the the Uninstaller folder is left
within $INSTALL_DIR in Windows 7.

for use with a 32 bit JRE.

Rationale:
On an x64 system using a 32 bit jvm Without the 32 bit libwrapper, messages
like this will be shown in wrapper.log with the wrapper in MTN & I2P >= 0.8.7:

-----------------------
 Launching a JVM...
 WrapperManager: Initializing...
 WrapperManager: 
 WrapperManager: WARNING - Unable to load the Wrapper's native library 'libwrapper.so'.
 WrapperManager:           The file is located on the path at the following location but
 WrapperManager:           could not be loaded:
 WrapperManager:             $I2P/lib/libwrapper.so
 WrapperManager:           Please verify that the file is both readable and executable by the
 WrapperManager:           current user and that the file has not been corrupted in any way.
 WrapperManager:           One common cause of this problem is running a 32-bit version
 WrapperManager:           of the Wrapper with a 64-bit version of Java, or vica versa.
 WrapperManager:           This is a 32-bit JVM.
 WrapperManager:           Reported cause:
 WrapperManager:             $I2P/lib/libwrapper.so: $I2P/lib/libwrapper.so: 
                           wrong ELF class: ELFCLASS64 (Possible cause: architecture word width mismatch)
 WrapperManager:           System signals will not be handled correctly.
-----------------------

With libwrapper.so removed, one sees the following:

 WrapperManager: WARNING - Unable to load the Wrapper's native library because none of the
 WrapperManager:           following files:
 WrapperManager:             libwrapper-linux-x86-32.so
 WrapperManager:             libwrapper.so
 WrapperManager:           could be located on the following java.library.path:
 WrapperManager:             $I2P
 WrapperManager:             $I2P/lib
 WrapperManager:           Please see the documentation for the wrapper.java.library.path
 WrapperManager:           configuration property.
 WrapperManager:           System signals will not be handled correctly.
-----------------------

The 32 bit lib names, when installed on an x64 system, will match the alternate
names that the wrapper looks for.

Fixed single quotes.
Email follows:

...


I attached file "snark-messages_pl.po.gz". I give you permission to use this file in I2PSnark distribution.
If you don't believe me that it is true polish translation, you can check it with some web translator.

Fist I used ordinary text editor to translate. Later I used Poedit <http://www.poedit.net/>.
And I don't know why it gives strange error messages when I save the file.

17:43:29: snark-messages_pl.po:172: a format specification for argument {0} doesn't exist in 'msgstr'
17:43:29: snark-messages_pl.po:177: a format specification for argument {0} doesn't exist in 'msgstr'
17:43:29: msgfmt: found 2 fatal errors

_______
greetz,
polacco

     and '9591822ae7297e11b8efacb8456758babb1c6505'

            to branch 'i2p.i2p' (head 0d92feaa69315781a8e98190c6d11b6b91355f8b)

Tested in Windows 7.
As has been customary, these were linked with gmp-5.0.2.

Built using 
"x86_64-w64-mingw32-gcc (GCC) 4.5.3" on Debian Sid with debug symbols stripped
using x86_64-w64-mingw32-strip.

     and '2b3daf42c48bc7b83cfa015b1dba87538ee2f8db'

The Tanuki Software website states "64-bit Windows versions of the Java Service Wrapper
are not currently being made available in the Community Edition." The Makefile
for x86_64 is missing from the upstream tarball as well. 

Well...included in this checkin is a diff against 
$WRAPPER-3.5.9-SRC/src/c/Makefile-windows-x86-32.nmake (see the README in
installer/libs/wrapper/win64.

- removing from /build.xml
- moving recent changes from installer/resources/postinstall.bat to installer/install.xml
- dropping installer/resources/postinstall.bat