StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Weirdness is highly subjective, I just suggest to follow the official recommendation:</p> <blockquote> <h3><a href="http://maven.apache.org/guides/mini/guide-naming-conventions.html" rel="noreferrer">Guide to naming conventions on groupId, artifactId and version</a></h3> <ul> <li><p><strong><code>groupId</code></strong> will identify your project uniquely across all projects, so we need to enforce a naming schema. It has to follow the package name rules, what means that has to be at least as a domain name you control, and you can create as many subgroups as you want. <a href="http://java.sun.com/docs/books/jls/third_edition/html/packages.html#7.7" rel="noreferrer">Look at More information about package names</a>.</p> <p>eg. <code>org.apache.maven</code>, <code>org.apache.commons</code></p> <p>A good way to determine the granularity of the groupId is to use the project structure. That is, if the current project is a multiple module project, it should append a new identifier to the parent's groupId.</p> <p>eg. <code>org.apache.maven</code>, <code>org.apache.maven.plugins</code>, <code>org.apache.maven.reporting</code></p></li> <li><p><strong><code>artifactId</code></strong> is the name of the jar without version. If you created it then you can choose whatever name you want with lowercase letters and no strange symbols. If it's a third party jar you have to take the name of the jar as it's distributed.</p> <p>eg. <code>maven</code>, <code>commons-math</code></p></li> <li><p><strong><code>version</code></strong> if you distribute it then you can choose any typical version with numbers and dots (1.0, 1.1, 1.0.1, ...). Don't use dates as they are usually associated with SNAPSHOT (nightly) builds. If it's a third party artifact, you have to use their version number whatever it is, and as strange as it can look.</p> <p>eg. <code>2.0</code>, <code>2.0.1</code>, <code>1.3.1</code></p></li> </ul> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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