I get the this error on every plugin.

I get this error on all my plugins:

(The type com.avaje.ebean.EbeanServer cannot be resolved. It is indirectly referenced from required .class files)

If I remove the Bukkit and Permissions from my build path then i don't get this error, but then I get much more other errors.

Does anybody know how to solve this?

 

I haven't come across this error :/
Have you changed the settings in eclipse at all, and does it affect your plugins at all?
by that i mean, is it just an unnecessary annoyance?

 

I have this error on al my plugins.
I didn't touched the settings from Eclipse.

 

Ok ik ben niet zeker over je probleem, maar ik denk dat het misschien iets te makenmet je te bouwen pad zijn. Of zelfs uw Eclipse werkruimte.
Misschien proberen om rond meer kijken?

 

Can you please talk Dutch without translator or just English.
But it didn't worked.

 

I think the problem consists of you haven't added the ebean library to your build-path.
If you compile bukkit hisself, Maven automatically gets it, so you just have to search for it on your pc.
That helped me with the same error

 

I only added Bukkit and Permissions.

 

Then try to add ebean, and I think, it should work

 

Where can i download eBean?
But earlier this wasn't needed.

 

Well, if you have compiled bukkit, you have already downloaded it (or rather Maven did it for you).
I found it on my computer when I looked in my bukkit-project's buildpath, so I can't give you a link, just look in the project-file, there you'll find the path

Don't know if this was needed before, started today with bukkit^^

 

Euh, i downloaded Bukkit here.
http://ci.bukkit.org/job/dev-Bukkit/lastSuccessfulBuild/artifact/target/bukkit-0.0.1-SNAPSHOT.jar

 

You may try the file from this link:
http://ovh.dl.sourceforge.net/project/ebeanorm/ebean-2.7.3.zip
(just the ebean-2.7.3.jar), but i haven't tested it

 

Thanks, I had the same problem. Downloaded the ebean 2.7.3 and added the ebean-2.7.3.jar to my project and it works now.

 

what is ebean in the first place by the way?

 

I would suggest just using the latest Bukkit Recommended Build, which is #495 as I'm writing this. It worked for me.

My guess is that it's a bug/feature introduced in the newer, less stable release. =P Until I'm told that EBean has become an official dependency for Bukkit, I'd rather not use it with my plugins.