Plugins (.jar-Files) are ignored by bukkit

Discussion in 'Plugin Development' started by Fensterbank, Jun 18, 2011.

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

    Fensterbank

    Hi,

    I have a small problem with Netbeans and I hope you can help here.
    Because of the better WebService-Handling of Netbeans in compare to Eclipse, I switched to it for developing plugins there.

    But at the moment I've the problem that bukkit ignores completely all Netbeans compiled plugins.
    Means, no messages, no errors, no response. It is like the file wouldn't be exists in the plugins folder.

    So I compared the content of the generated .jar-files.

    The file compiled by Netbeans does have the packages folder, but NOT the files .classpath, .project and plugin.yml.
    Normally, bukkit will give an error, if only the plugin.yml is missing, so this can't be the cause for ignoring the whole existence of the plugin file. ;)

    Is it the missing .classpath and .project?

    And how can I say to Netbeans, which additional files (like plugin.yml) have to be included?

    Thanks a lot!
     
  2. Offline

    CainFoool

    .classpath and .project are useless, those are only if you are sharing the source to your plugin.
    Whenever you are exporting the .JAR check to make sure you are exporting with the right options, I had this problem first time.
     
  3. Offline

    garbagemule

    plugin.yml is the only file you need to worry about here. Like Cain says, the .classpath and .project files are annoying bloat that IDEs tend to drop in your project folder. Do not include these in your plugin jars, as they first of all aren't used, and second of all just add to the file size (every byte counts ;)).
     
  4. Offline

    Fensterbank

    Okay, thanks for your replies.
    Good to know, the .*-Files are unused, so they can stay out.
    I added the plugin.xml manually and now it works.
    I was a little embarrassed because all I know bukkit would complain about the missing plugin.yml.
    But after the ignoring of the .jar-Files I tought, this wouldn't be the problem. Tought wrong.

    So problem solved. Thanks :)
     
  5. Offline

    nickguletskii

    Just a little suggestion - make an ant buildfile to aid compilation and debugging.
     
  6. Offline

    Acrobot

    I had this problem too, NetBeans didn't generate .class files, so I did rebuild the project from scratch, copied old sources and it worked :)
     
  7. Offline

    AlbireoX

    Also, make sure to clean and build each time you test/release/build! Put the plugin.yml into the default package -- that is, just create it under the Source Packages folder. You don't need to add it manually.

    A good thing too is to make Bukkit a library. Generate javadocs for it too! It really helps!
     
Thread Status:
Not open for further replies.

Share This Page