UsingCarbonTouchpoint.md

Using Carbon

In Carbon 5, there are product-specific runtimes, which the developer will not know about at the time of creating the feature. In order to support dynamically copying files to the runtime location during feature installation, WSO2 has introduced a custom touchpoint.

Shown below is a sample of p2.inf in order to copy a particular file to a runtime location:

metaRequirements.0.namespace = org.eclipse.equinox.p2.iu
metaRequirements.0.name = org.wso2.carbon.p2.touchpoint

instructions.configure = \
org.wso2.carbon.p2.touchpoint.copy(source:${installFolder}/../lib/features/org.wso2.carbon.touchpoint.sample_${feature.version}/bin/,target:${installFolder}/../{runtime}/bin/, overwrite:true);\
org.wso2.carbon.p2.touchpoint.copy(source:${installFolder}/../lib/features/org.wso2.carbon.touchpoint.sample_${feature.version}/conf/osgi/launch.properties,target:${installFolder}/../{runtime}/conf/osgi/launch.properties, overwrite:true);\

• {runtime}: which is replaced with the runtime name at the feature installation

This custom touchpoint should be available in the p2-repo. Therefore it should be added to generate-repo goal as below in the product generation:

    <plugin>
        <groupId>org.wso2.carbon.maven</groupId>
        <artifactId>carbon-feature-plugin</artifactId>
        <executions>
            <execution>
                <id>p2-repo-generation</id>
                <phase>package</phase>
                <goals>
                    <goal>generate-repo</goal>
                </goals>
                <configuration>
                    <targetRepository>file:${basedir}/target/p2-repo</targetRepository>
                    <features>
                        <feature>
                            <id>org.wso2.carbon.p2.touchpoint.feature</id>
                            <version>${carbon.maven.version}</version>
                        </feature>
                    </features>
                </configuration>
            </execution>
            ...
        </executions>
        ...
    </plugin>