Always run OSGi HTTP service on random port in itests (#11523)
It is probably always a good idea to run the OSGi HTTP service on a random available port in itests. So when this is always done it prevents future issues and removes a bit of duplication. Signed-off-by: Wouter Born <github@maindrain.net>
This commit is contained in:
@@ -38,6 +38,7 @@
|
||||
|
||||
<properties>
|
||||
<m2e.jdt.annotationpath>target/dependency</m2e.jdt.annotationpath>
|
||||
<org.osgi.service.http.port>9090</org.osgi.service.http.port>
|
||||
</properties>
|
||||
|
||||
<dependencies>
|
||||
@@ -179,6 +180,24 @@
|
||||
</bndruns>
|
||||
</configuration>
|
||||
</plugin>
|
||||
<plugin>
|
||||
<groupId>org.codehaus.mojo</groupId>
|
||||
<artifactId>build-helper-maven-plugin</artifactId>
|
||||
<executions>
|
||||
<execution>
|
||||
<id>reserve-network-port</id>
|
||||
<goals>
|
||||
<goal>reserve-network-port</goal>
|
||||
</goals>
|
||||
<phase>process-resources</phase>
|
||||
<configuration>
|
||||
<portNames>
|
||||
<portName>org.osgi.service.http.port</portName>
|
||||
</portNames>
|
||||
</configuration>
|
||||
</execution>
|
||||
</executions>
|
||||
</plugin>
|
||||
</plugins>
|
||||
</build>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user