Google Git
Sign in
apache / sling-feature-launcher-maven-plugin / 59f8ab6cd24c325655cb71bec230f865a9cf27ff
commit59f8ab6cd24c325655cb71bec230f865a9cf27ff[log] [tgz]
authorRobert Munteanu <rombert@apache.org>Mon Jul 18 16:36:46 2022 +0300
committerRobert Munteanu <robert.munteanu@gmail.com>Mon Jul 18 15:45:34 2022 +0200
tree97c06180e6414d8f78470d8438052b606d564247
parent15236c7f4517d299e34335dba21bc99a09b65659 [diff]
Revert "SLING-11442 - Allow blocking after the features have been launched"

This reverts commit 15236c7f4517d299e34335dba21bc99a09b65659, as this overlaps
with the work from SLING-10364 and it's not yet clear what a "proper" solution is.
1 file changed
tree: 97c06180e6414d8f78470d8438052b606d564247
  1. src/
  2. .asf.yaml
  3. .gitignore
  4. CODE_OF_CONDUCT.md
  5. CONTRIBUTING.md
  6. Jenkinsfile
  7. LICENSE
  8. pom.xml
  9. README.md
README.md

Apache Sling

Build Status Test Status Coverage Sonarcloud Status JavaDoc Maven Central License

This module is part of the Apache Sling project.

This plugin allows starting and stopping feature model applications without blocking the Maven execution. It is intended mainly for usage with integration tests.

Usage

Configure the plugin as follows:

<plugin>
    <groupId>org.apache.sling</groupId>
    <artifactId>feature-launcher-maven-plugin</artifactId>
    <configuration>
        <launches>
            <launch>
                <id>model</id>
                <!-- optionally uncomment to skip this launch if the skip property resolves to false -->
                <!--
                <skip>${prop1.skip}</skip>
                -->
                <feature>
                    <groupId>org.apache.sling</groupId>
                    <artifactId>org.apache.sling.starter</artifactId>
                    <version>12</version>
                    <classifier>oak_tar</classifier>
                    <type>slingosgifeature</type>
                </feature>
                <launcherArguments>
                    <!-- optionally uncomment to pass any required extra vm options -->
                    <!--
                    <vmOptions>
                        <value>-Xmx512m</value>
                        <value>-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5000</value>
                    </vmOptions>
                    -->
                    <frameworkProperties>
                        <org.osgi.service.http.port>8080</org.osgi.service.http.port>
                    </frameworkProperties>
                    <!-- Feature launcher variables can be set like this -->
                    <variables>
                        <TEST_VARIABLE>TEST_VALUE</TEST_VARIABLE>
                    </variables>
                </launcherArguments>
                <startTimeoutSeconds>180</startTimeoutSeconds>
            </launch>
        </launches>
        <toLaunch>
        </toLaunch>
    </configuration>
    <executions>
        <execution>
            <goals>
                <goal>start</goal>
                <goal>stop</goal>
            </goals>
        </execution>
    </executions>
</plugin>

This will run the Sling Starter using the oak_tar aggregate, setting the HTTP port to 8080 and waiting for up to 180 seconds for the application to start.

The start goal is bound by default to the pre-integration phase and the stop goal to the post-integration-test one.

See the src/it folder for a complete example, including a configuration of the maven-failsafe-plugin.