Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat package naming convention do you use for personal/hobby projects in Java?
    primarykey
    data
    text
    <p>I'm already familiar with the standard Java package naming convention of using a domain name to create a unique package name (i.e. package <code>com.stackoverflow.widgets</code>). However, I've never seen any recommendations for how to choose package names for personal projects. I assume because this is because this is really a matter of personal taste.</p> <p>So, how do you choose package names for personal projects that will never make it into production (you might be experimenting with a new framework in your spare time). Assuming you don't have a personal website whose domain you can use to create your package structure, what do (or would) you do? Do you have a logical system in place for generating new package names for hobby projects, or do you just use simple throw-away package names like <code>mypackage</code>?</p> <p>Since I'm just curious to see what different people's thoughts are on this, I've made this a community wiki.</p> <p>For me personally, I've never given it much thought, but I wanted to play around with <a href="http://wicket.apache.org/" rel="noreferrer">Wicket</a> tonight and it occurred to me that I don't have a clear idea of how I want to organize my hobby projects. A separate, distinct package naming convention for hobby projects (in my mind, at least) would serve as a good way to keep personal and work-related code clearly separate from each other.</p> <p>I was thinking of a simple hierarchal naming convention, to keep the source for my personal projects in a single root folder:</p> <ul> <li>Use <code>myprojects</code> as the root folder </li> <li>Append the project name </li> <li>Add any additional subpackage names</li> </ul> <p>So, my Wicket project would be in the package <code>myprojects.learningwicket</code> and unit tests would be in the package <code>myprojects.learningwicket.tests</code> (for example).</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload