Great to see a working java-wrapper, so you don't have to use (visual)
c++ ;). Thanks a lot!
I tried to use the trunk-version, because I had trouble with
references/equal-stuff.
JBridge loads but can't find my factory and thus doesn't load my bot.
Things used to work out, when using 0.2-alpha, did anything change in
the loading-process?
If not, are there any other steps to do, when using the svn-version? I
did the following:
- exporting bwapi-bridge.jar and bwapi-unit.jar via eclipse und copy
it to ".../AI/"
- compiling bwapi-bridge.dll with vc++ and copy it to [...]/AI/
- reexporting mybot.jar (my bot) and copy it.
greetings,
Martin
You have taken the right steps. There are many changes to the trunk.
One of them is whether I print on the screen that I found your bot. So
it's possible your bot is found but just doesn't show anything. You
can turn on more debugging out put by uncommenting the BRIDGE_DEBUG
directive in BridgeAIModule.h, but it will also enable debugging per
http://code.google.com/p/bwapi-jbridge/issues/detail?id=2. If you
want, you can change suspend from 'n' to 'y' and put a breakpoint in
the code where the bot is discovered.
Also, make sure you have BWAPI 2.4 since 2.5 support isn't there (but
will be very shortly). Note, bwapi-unit trumps any bot you have if you
are using the Service Provider mechanism (i.e. the file META-INF/
services/org.bwapi.bridge.BridgeBotFactory). So it may be best to take
the bwapi-unit JAR off the classpath (out of the AI folder) if you're
not using JUnit.
Finally, for the obvious stuff...make sure you have built your JAR on
the trunk version (which has more methods in the iface) and make sure
the META-INF/services/org.bwapi.bridge.BridgeBotFactory has a line w/
the FQCN of your bot factory. Other than all that, I am not sure. I
may ask you to email me your project (w/ any sensitive stuff taken
out) so I can see myself.
Also note, I am getting close to committing 2.5 support (really just
one method change) and the complete impl of BWSAL's latest version
(untested). My plans are to add gobs of logging (slf4j on java side
and log4cxx on c++ side), gobs of configuration options in an ini
file, and JSR-299 (Weld from Seam) support in a separate for events
and dependency injection which will be frekin awesome. Once I do that,
I will tag and do another version (still alpha cuz that pesky 64 bit
issue). It should be coming soon.