Eclipse can't resolve packages with RB 670 & 733

Discussion in 'Plugin Development' started by xZise, Apr 10, 2011.

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

    xZise

    Hello,
    I tried today to test my plugin against RB 670. So I checked out the newest commit of the Bukkit git repository and reloaded Eclipse. But after a rebuild eclipse remarks in my main class:
    What did I wrong? I never used ebean, and I have no clue what ebean is, but I can see, that the Bukkit project itself has ebean in its build path.

    So how could I fix this?

    Fabian
     
  2. Offline

    Sammy

    Ebean is for persistence (look at my tutorial on resources), I think that's and error that already been fixed a few commits ago, are you sure you are using a recent build ? :confused:
     
  3. Offline

    xZise

    Code:
    Previous HEAD position was d208614... Just NAG once, to be nice
    HEAD is now at ef5d72e... Added bed events and methods.
    This is the newest bukkit commit since 3 days.

    Fabian
     
  4. Offline

    xZise

    Okay, even with the newest commits I'm impossible to test the plugins. Here is what I'm doing:
    1. Fetch the upstream remote (= the official remote repository)
    2. Checkout upstream/master which should be the newest commit.
    3. Reload the Bukkit project
    4. All projects which depends on Bukkit will now have the error
    Is there no way to fix this? I mean I'm the only developer who use Eclipse with Bukkit as project?

    [edit]Okay I could fix this, but only if I always add ebeans to the dependencies of all plugin projects. So maybe Eclipse isn't resolving dependencies of dependencies?![/edit]

    Fabian
     
Thread Status:
Not open for further replies.

Share This Page