Usually if you have a multi-module build you should have the following structure:
+-- parent (pom.xml)
+-- module-1 (pom.xml)
+-- module-2 (pom.xml)
which means also having the parent being located in the trunk of your VCS (in this case SVN).
Furthermore the result of the above structure is that your parent looks similar like this:
<modelVersion>4.0.0</modelVersion>
<groupId>com.company.logreport</groupId>
<artifactId>parent</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>pom</packaging>
<modules>
<module>logreport-client</module>
<module>logreport-common</module>
<module>logreport-server</module>
</modules>
and the scm information which will be defined in the parent only once like this:
<scm>
<developerConnection>scm:svn:svn://[hidden]/svn/infra/trunk/</developerConnection>
<connection>scm:svn:svn://[hidden]/svn/infra/trunk/</connection>
<url>svn://[hidden]/svn/infra/trunk/</url>
</scm>
Apart from that you should never define passwords in your pom. The intended place for such things is the settings.xml.
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd">
...
<servers>
<server>
<id>svn-server</id>
<username>my_login</username>
<password>my_password</password>
</server>
</servers>
...
</settings>