Maven profiles can only be copntrolled by system properties and not

Maven properties of a parent POM. The presence of the "ldi.releaseBuild"
is a good match for the activation conditions of "with-mobile" and
"with-not-android-relevant". It currently seems that in
buildAndUpdataProduct.sh the profiles are correctly activated and
deactivated. So this could also correctly work for local builds.

java/com.sap.sailing.domain.shared.android/pom.xml

@@ -42,8 +42,7 @@
 			<id>with-mobile</id>
 			<activation>
 				<property>
-					<name>mobile.build.is.default</name>
-					<value>true</value>
+					<name>ldi.releaseBuild</name>
 				</property>
 			</activation>
 			<build>