Bukkit won't recognize updated plugin

Hey guys, having a very odd issue here.

So I had a plugin that I developed to help me facilitate granting permissions. It has worked fine for quite some time, until the other week I updated it to add a new function, and updated another plugin to use this function. When I did a /reload, I saw the following error:

Code:

 Error occurred while enabling Edit v0.8 (Is it up to date?)
java.lang.NoSuchMethodError: com.thepastimers.Permission.Permission.registerPermission

It was only after putting a getLogger().info line in the init function (which didn't show up at all), then changing a line that did exist and was already outputting properly (just in case the newly added line had an error of some sort) which also didn't show up that I realized that bukkit was ignoring my changes to the plugin.

I then went through the following steps:

1. Rebuilt both jars, copied them over, then /reload
2. Deleted Permission.jar, did /reload, then added it back to the server and again /reload
3. Restarted the server
4. Did a completely clean build on the Permission plugin (cleaned out the class files), deleted the plugin from the server, stopped the server, started the server without the plugin, stopped it again, added the plugin back, and restarted the server.

None of these things have fixed the problem. I have verified by using a JAR decompiler that the jar being generated has the updated code. I have verified that the jar on the server matches the jar that I have compiled. I have tested this jar on another server and it seems to work fine (though I think the other server may be a different version of bukkit). No matter what I do, bukkit refuses to load the updated code, though it will change the version of the plugin if I change it in the plugin.yml. Other plugins update fine.
Any ideas as to why this is happening? I'm not interested in any substitute plugins, I'd much rather figure out why this one isn't working.

 

make sure that no plugin share same package in any way.

 

Do you mean that no plugin should have the same package name as another? The base package, com.thepastimers, is shared across all my plugins.