THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Code Block |
---|
<plugin> <groupId>org.apache.geronimo.buildsupport</groupId> <artifactId>car-maven-plugin</artifactId> <configuration> <deploymentConfigs> <!-- gbean deployer is default. For jee apps include all deployers your app needs, see properties --> <deploymentConfig>${gbeanDeployer}</deploymentConfig> <deploymentConfig>${j2eeDeployer}</deploymentConfig> <deploymentConfig>${jetty6Deployer}</deploymentConfig> <deploymentConfig>${jasperDeployer}</deploymentConfig> <!--<deploymentConfig>${jpaDeployer}</deploymentConfig>--> </deploymentConfigs> <!-- if you are deploying a jee app specify it here --> <module> <groupId>com.liferay</groupId> <artifactId>liferay-portal<portal-lesslibs</artifactId> <version>${liferayVersion}</version> <type>war</type> </module> <!-- Normally you can use the maven dependencies unaltered. If you need to specify import scope you can list the dependencies here as you want them in the plan.xml --> <useMavenDependencies> <value>true</value> <includeVersion>true</includeVersion> </useMavenDependencies> <!-- the instance sets up most of the optional geronimo-plugin.xml content --> <instance> <plugin-artifact> <!-- extract stuff from the car to the specified location (good for config info --> <!--<copy-file relative-to="server" dest-dir="var/roller-data">themes</copy-file>--> <!-- content that should go into var/config/config.xml for module customization --> <!-- note the variable ${LiferayContextPath} which is further specified in var/config/config-substitutions.properties --> <config-xml-content server="default"> <gbean name="org.apache.geronimo.plugins/liferay-jetty/${liferayPluginVersion}/car"> <attribute name="contextPath">${LiferayContextPath}</attribute> </gbean> </config-xml-content> <!-- a user-tweakable variable to go into var/config/config-substitutions.properties --> <config-substitution key="LiferayContextPath">/liferay</config-substitution> </plugin-artifact> </instance> </configuration> </plugin> |
...