Solved Naming package

Discussion in 'Plugin Development' started by Robnoo, Dec 10, 2018.

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

    Robnoo

    Hi,

    I already created some plugins and I've always used me.robnoo.<projectname> as 'mainpackage' because the first tutorial I saw used that same structure. I recently found an old thread: https://bukkit.org/threads/on-namespaces-please-do-not-use-bukkit-in-your-plugins.3732/. Their, the advice is given of using yourcountry.yourname.*.
    It left me with some questions after reading it:
    Are there rules for naming packages (apart from 'don't use special symbols',etc.)?
    Can I use this pickage name (me.robnoo.<projectname>) or should I change it?
    Can you buy/claim a domain name?

    Thank you in advance,
    Robnoo
     
  2. Online

    timtower Administrator Administrator Moderator

    @Robnoo Make sure that the packages are unique for your projects, you could get massive conflicts otherwise, so using the projectname is generally a good thing to do.
    There are conventions, but you are following them already.
    The me.robnoo seems fine to me.
    You can indeed buy a domain name, pretty much all webhosting services provide this. Domain without website is a bit useless though.
     
  3. Offline

    Robnoo

    Thank you very much!

    Robnoo
     
Thread Status:
Not open for further replies.

Share This Page