On namespaces - please do NOT use *.bukkit in your plugins.

Discussion in 'Plugin Development' started by EvilSeph, Feb 8, 2011.

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


    Yes, you can.
    For me, I've always done me.justcool393.PluginName since I don't have a domain, but it's advisable to use a domain (such as com.stuff.PluginName) if you have one.
  2. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    But who owns the domain justcool393.me? Your package matches a domain you don't own. ;)
  3. Offline


    I'm using de.janmm14.<insert plugin name>
    I don't think if someone gets the domain janmm14.de he's developing java applicatios or bukkit plugins.

    But in de.janmm14 my country and my nick are included and I think that's the best if you don't own a domain.
  4. Offline

    mbaxter ʇıʞʞnq ɐ sɐɥ ı

    If you don't own the domain, it's a scummy move to use it. There's lots of other suggested solutions which work nicer, such as emailprovider.username (package com.gmail.myemailaddress).
    daboross likes this.
  5. Offline


    Ah, dang TLD's. Anyway, I've always used me.justcool393.<whatever> as the package name. I think I got that naming convention from some tutorial or something and stuck with it.
  6. Offline


  7. Offline


    I use me.<myusername>.<myplugin>
  8. Offline


    1. me.dudemister.<plugin>.<subPluginInfo>

    Mine. I own the site, too.
  9. I wonder when this turned into a "what namespace do you guys use?" discussion thread...
    blobic123 and FerusGrim like this.
  10. Offline


    AdamQpzm Right... wait for it... now!
Thread Status:
Not open for further replies.

Share This Page