Added license info to pom.xml, extended next release howto for maven

git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/branches/pmd/4.3.x@7366 51baf565-9d33-0410-a72c-fc3788e3496d

pmd/etc/doing_the_next_pmd_release.txt

@@ -80,3 +80,29 @@ Submit news to SF
 Go to http://freshmeat.net/
 Submit news to java.net
 Do a blog entry
+
+
+Getting the new PMD version into Maven Central Repository:
+----------------------------------------------------------
+1. Make sure you have a gpg key:
+
+   gpg --list-keys
+
+2. Create a bundle
+
+  mvn clean source:jar javadoc:jar package gpg:sign repository:bundle-create -Dgpg.keyname=your_key -Dgpg.passphrase=your_pwd
+
+3. The bundle is target/pmd-x.x.x-bundle.jar.
+
+  Test it: target/pmd-x.x.x.jar is the file, that is contained in the bundle.
+  So we can use it:
+  
+  java -cp target/pmd-x.x.x.jar:lib/asm-3.2.jar:lib/javacc.jar:lib/jaxen-1.1.1.jar net.sourceforge.pmd.PMD src/net/sourceforge/pmd/PMD.java text unusedcode
+
+  This should work: "No problems found!"
+  
+
+4. Upload pmd-x.x.x-bundle.jar to https://oss.sonatype.org.
+
+More info: https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+Maven+Central
+

pmd/pom.xml

@@ -33,6 +33,13 @@
     </notifiers>
   </ciManagement>
   <inceptionYear>2002</inceptionYear>
+  <licenses>
+    <license>
+      <name>BSD-style</name>
+      <url>http://pmd.sourceforge.net/license.html</url>
+      <distribution>repo</distribution>
+    </license>
+  </licenses>
   <mailingLists>
     <mailingList>
       <name>PMD development</name>