Foren
Maven and liferay-plugin-package.properties
caio marcelo formiga, geändert vor 14 Jahren.
Maven and liferay-plugin-package.properties
New Member Beiträge: 7 Beitrittsdatum: 05.11.09 Neueste Beiträge
Hi Liferay Community,
According to this link I don’t need to depend on Plugins SDK to compile and package my portlet into WAR, since I can use the Eclipse. Actually, I`m using Maven as build tool and library manager.
So, still according to above link, the file liferay-plugin-package.properties is used to describes the plugin to Liferay's hot deployer. One of
the things that can be configured in this file is dependency .jars. If a portlet plugin has dependencies on particular .jar files that already come with Liferay, you can specify them in this file and the hot deployer will modify the .war file on deployment so that those .jars are on the class path. The link suggest that my file should be like this:
The attached image list all jars that comes at $LIFERAY_HOME/lib. Now comes my doubt. If my project depends on xml-api.jar what should I do?
put at my pom.xml file this dependency as follow? Or maybe add the <scope>provided</scope> tag? Or just omit this dependency from pom.xml and let Liferay Portal and the liferay-plugin-package.properties do its work:
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.0.b2</version>
</dependency>
Best Regards,
Caio Formiga
According to this link I don’t need to depend on Plugins SDK to compile and package my portlet into WAR, since I can use the Eclipse. Actually, I`m using Maven as build tool and library manager.
So, still according to above link, the file liferay-plugin-package.properties is used to describes the plugin to Liferay's hot deployer. One of
the things that can be configured in this file is dependency .jars. If a portlet plugin has dependencies on particular .jar files that already come with Liferay, you can specify them in this file and the hot deployer will modify the .war file on deployment so that those .jars are on the class path. The link suggest that my file should be like this:
name=Sample ICEfaces JSF 1.2 Sun Facelets
module-group-id=liferay
module-incremental-version=1
tags=sample
short-description=This plugin shows how to use ICEfaces and the JSF 1.2 Sun RI and the Facelets view-handler within Liferay. Requires Tomcat 6.x, GlassFish 2.0.x, or JBoss AS 4.2.x since JSF 1.2 has a JRE5 dependency.
change-log=
page-url=http://www.liferay.com
author=Liferay, Inc.
licenses=MIT
portal-dependency-jars=\
commons-beanutils.jar,\
commons-collections.jar,\
commons-digester.jar,\
commons-fileupload.jar,\
commons-lang.jar,\
commons-validator.jar,\
oro.jar
speed-filters-enabled=false
The attached image list all jars that comes at $LIFERAY_HOME/lib. Now comes my doubt. If my project depends on xml-api.jar what should I do?
put at my pom.xml file this dependency as follow? Or maybe add the <scope>provided</scope> tag? Or just omit this dependency from pom.xml and let Liferay Portal and the liferay-plugin-package.properties do its work:
<dependency>
<groupId>xml-apis</groupId>
<artifactId>xml-apis</artifactId>
<version>1.0.b2</version>
</dependency>
Best Regards,
Caio Formiga
caio marcelo formiga, geändert vor 14 Jahren.
RE: Maven and liferay-plugin-package.properties
New Member Beiträge: 7 Beitrittsdatum: 05.11.09 Neueste Beiträge
Sorry,
Now follows the attached image with the list of all jars that comes at $LIFERAY_HOME/lib.
Now follows the attached image with the list of all jars that comes at $LIFERAY_HOME/lib.
Anhänge:
Lisa Simpson, geändert vor 14 Jahren.
RE: Maven and liferay-plugin-package.properties
Liferay Legend Beiträge: 2034 Beitrittsdatum: 05.03.09 Neueste Beiträge
This should probably be in "Development" and not "Setup"
Milen Dyankov, geändert vor 14 Jahren.