#497 Bukkit error - cannot be resolved.

Discussion in 'Plugin Development' started by Major, Apr 1, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    Major

    Whenever I use the #497 version of Bukkit (I was coding a plugin and downloaded it) i get the following error.

    I managed to find my #495 one and that doesn't bring up the error, so I was wondering what causes it.

    OS: Vista
    32-bit
    IDE: Eclipse
     
  2. Offline

    mughi

    moving to plugin development, but you are going to get asked why you are over 100 revisions behind
     
  3. Offline

    Plague

    He means bukkit, not craftbukkit. Well it's not a recommended build and I do not have time (hell where did my time go since promoting to a moderator, hmm) I cannot confirm.

    If there is someone who can confirm this, please say so and then you can file a bug I guess.
     
  4. Offline

    Major

    As plague said, bukkit not CraftBukkit. It even says bukkit in the title... and the post?

    @Plague Another type just started again with the 495 so I'm going to restart my PC, remove every bukkit related jar I have, and see from there.
     
  5. Offline

    Plague

    It's easy for a non plugin developer to be confused since nearly everybody here says bukkit and means craftbukkit...
     
  6. Offline

    mughi

    sorry.. reading comprehension fail..
     
  7. Offline

    Arcwolf

    confirmed. Solution, http://sourceforge.net/projects/ebeanorm/files/ download ebean 2.7.3 zip and extract the ebean-2.7.3.jar place it in a directory of your choosing and go to a project file in eclipse. Options, Java Buildpath, Libraries, add an external jar select the ebean-2.7.3.jar you extracted.

    That fixed it for me. Recompiled my project. Tested in CraftBukkit server 602. Seemed to work ok. <shrugs> Maybe one of those future Oops I broke your plugin thingies?
     
  8. Offline

    ssell

    This does fix it but should not be treated as a true fix.

    This issue was discussed on #Bukkitdev and it was suggested to go back to 493 until a real fix is made.
     
  9. Offline

    Major

    Ahh, excellent. Don't suppose you have a 493 link?

    @mughi apologies, that comment wasn't intended to sound rude.
     
  10. Offline

    Arcwolf

  11. Offline

    ssell

  12. Offline

    Major

    Wonderful, thankyou :)
    If this appears to an error, could I suggest making a sticky about it to avoid more of these topics (which will undoubtedly happen).

    @ssell ninja'd by Arcwolf ;)
     
  13. Offline

    ssell

    Blast!

    This error was bothering me earlier today (before it came to the attention of dinnerbone), so am happy we were able to help you out with it.
     
  14. Offline

    Major

    Yes, thankyou for this :) Using 493 fixed everything up.
     
  15. Offline

    Roujo

    Using #495 also works. =)
     
Thread Status:
Not open for further replies.

Share This Page