News:

Holy shit, it's 2018 2019 2020 2021 2022 2023 2024, and the US isn't a fascist country! What a time to be alive.

Main Menu

Updating a plugin to javaop 2.1.3 lost in forest

Started by ilaggoodly, May 13, 2010, 12:10:10 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ilaggoodly

Right, so I'm trying to update my old plugin VIPWatch to javaop 2.1.3 (you can find it in the archive) and I must say getting the whole thing imported correctly in eclipse was quite the trip, but eventually I got it working to the point where there are no warnings in eclipse... however it won't get noticed by Javaop at all


Loading plugin: com.javaop.UserManagement.PluginMain
Loading plugin: null
Unable to load plugin file: jar:file:///T:\tmp\JavaOp_2.1.3_RC1\Plugins\VIPWatch.jar!/
java.lang.NullPointerException
       at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
       at java.lang.ClassLoader.loadClass(Unknown Source)
       at java.lang.ClassLoader.loadClass(Unknown Source)
       at com.javaop.pluginmanagers.PluginManager.loadFile(Unknown Source)
       at com.javaop.pluginmanagers.PluginManager.loadFile(Unknown Source)
       at com.javaop.pluginmanagers.PluginManager.initialize(Unknown Source)
       at com.javaop._main.BotStart.main(Unknown Source)
Loading plugin: com.javaop.Version.PluginMain


Sort of a cryptic error message to me, what could be causing this? Were there some changes that might have subtly broke the code inside my plugin or is it more likely that its my fault?


EDIT: I was going to post the code... but can't attach and my webserver is bitching :(

Joe

Yeah, there was a major change to how plugins are loaded. I thought I maintained backwards compatibility, but obviously not.

I would check out the SVN repository, add your plugin source code there, and modify the build.xml to build it along with the rest of the code.
Quote from: Camel on June 09, 2009, 04:12:23 PMI'd personally do as Joe suggests

Quote from: AntiVirus on October 19, 2010, 02:36:52 PM
You might be right about that, Joe.


Lance

Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

Lance

If the above does not resolve your issue, make sure you have no uppercase letters in your package names. It sounds strange, I know... But, yesterday when I was creating a plugin, I ran into the same problem. Lowercased package names and the error is gone ;)
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!

ilaggoodly

Ah, well i think it might have been me just missing the mysql connector, anyway after adding to source & build.xml, it worked. Thanks! The new version of the bot seems to be a lot more stable than the last, I had given up on the project because it was losing connection to battlenet once every 2 days or so!

Return of VIPWATCH!

http://rylai.de/vip/nsg/

Joe

Is it still losing connection, but reconnecting? Or just not losing connection? If it's the second one then I think it's something on your end.. I don't think I fixed anything connection wise, except fixing stayconnected.. if I even did that. :P
Quote from: Camel on June 09, 2009, 04:12:23 PMI'd personally do as Joe suggests

Quote from: AntiVirus on October 19, 2010, 02:36:52 PM
You might be right about that, Joe.


ilaggoodly

I think its not disconnecting at all anymore... but its sort of hard to tell because of the massive text my plugin generates in the logs/cmdline ^^

Lance

I found the problem... The manifest needs an empty line at the end. Yay for uppercase package names :D
Quote from: Joe
[23:55:31] [william@enterprise ~/Documents/Programming/javaop2]$ svn commit -m 'Tried to fix StayConnected. Again.'
Committed revision 63.
StayConnected strikes back!