Merge branch 'maven-repo' into 'master'

Maven repo

At least the snapshot deployment works.
When we are ready to release 1.0, we need to test if this also works, as a release needs to comply with stricter rules.
To see the changed needed on settings.xml, look at #52

See merge request !9

pom.xml

@@ -39,18 +39,22 @@
 			<id>chw</id>
 			<name>Christian Wulf</name>
 			<email>chw@informatik.uni-kiel.de</email>
+			<organization>Christian-Albrechts-Universitaet zu Kiel</organization>
+			<organizationUrl>http://www.se.informatik.uni-kiel.de/en/team/christian-wulf</organizationUrl>
 		</developer>
 		<developer>
 			<id>ntd</id>
 			<name>Nelson Tavares de Sousa</name>
 			<email>ntd@informatik.uni-kiel.de</email>
+			<organization>Christian-Albrechts-Universitaet zu Kiel</organization>
+			<organizationUrl>http://www.se.uni-kiel.de/en</organizationUrl>
 		</developer>
 	</developers>
 
 	<scm>
 		<connection>scm:git:https://build.se.informatik.uni-kiel.de/gitlab/chw/teetime.git</connection>
 		<developerConnection>scm:git:ssh://gitlab@build.se.informatik.uni-kiel.de:chw/teetime.git</developerConnection>
-		<url>http://teetime.sourceforge.net</url>
+		<url>https://build.se.informatik.uni-kiel.de/gitlab/chw/teetime/</url>
 	</scm>
 
 	<repositories>
@@ -191,7 +195,7 @@
 				<configuration>
 					<serverId>ossrh</serverId>
 					<nexusUrl>https://oss.sonatype.org/</nexusUrl>
-					<autoReleaseAfterClose>true</autoReleaseAfterClose>
+					<autoReleaseAfterClose>false</autoReleaseAfterClose>
 				</configuration>
 			</plugin>