Go to file
Brian Chan 0b01463efb LPS-104973 2020-04-15 18:37:31 -07:00
dependencies LPS-104973 2020-04-15 18:37:31 -07:00
ext LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
gradle/wrapper LPS-71117 Update Gradle to 3.5.1 2018-09-24 16:19:47 -07:00
hooks LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
layouttpl LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
lib LPS-65815 remove references to osgi 2016-05-12 14:38:07 -07:00
misc Update copyright date, use -present 2014-04-04 22:04:59 -07:00
osgi/lib/plugin LPS-42644 Move dir to match core 2013-11-28 11:17:12 -08:00
portlets LPS-103848 SF 2020-02-21 11:14:09 -08:00
shared LPS-74544 SF 2017-12-05 10:08:56 +08:00
themes LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
tools/templates LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
webs LPS-104540 Add portal 7.3 version to plugins 2019-11-13 15:35:46 -08:00
.gitattributes LPS-64991 Force ivy.xml files to Unix line endings, so checksums match 2016-04-27 16:48:10 -07:00
.gitignore LPS-71117 Ignore .gradle directories 2018-09-24 16:20:08 -07:00
CONTRIBUTING.markdown LPS-66853 Auto SF 2016-09-22 11:57:43 +08:00
README.markdown LPS-66853 Auto SF 2016-09-22 11:57:43 +08:00
build-common-ivy.xml LRQA-28693 Use the regular "get" if "mirrors-get" isn't available yet 2017-02-06 14:44:21 -08:00
build-common-node.xml LPS-72572 Fix NPM invocation on Unix 2017-05-30 10:17:01 -07:00
build-common-plugin.xml LPS-101026 Remove com.liferay.xml.formatter 2019-09-27 09:41:55 -07:00
build-common-plugins.xml LPS-66853 Auto SF 2016-09-22 11:57:43 +08:00
build-common.xml LPS-94999 Sort options alphabetically 2019-05-25 18:08:17 -05:00
build.gradle LRCI-1166 Update poshi runner version to 1.0.258 2020-03-27 20:58:45 -07:00
build.properties Revert "LPS-86406 Add spring.configurator support and disable it by default" 2018-11-27 11:31:25 -08:00
build.xml Simplify build-summary 2018-04-06 15:00:48 -07:00
checkstyle-suppressions.xml LPS-52675 Skip all files for now 2016-10-25 19:40:55 -07:00
ci.properties LRQA-46827 Add LRCI to jira.project.keys 2019-03-11 21:49:27 -07:00
common.bnd LPS-47133 Build problem caused by bnd in China 2014-05-27 20:25:29 -07:00
copyright.txt Update copyright date, use -present 2014-04-04 22:04:59 -07:00
gradlew LPS-71117 Update Gradle to 3.5.1 2018-09-24 16:19:47 -07:00
gradlew.bat LRQA-29926 Add gradle for running poshiRunner 2017-01-24 11:29:28 -08:00
ivy-settings-publisher.xml LPS-66853 Auto SF 2016-09-22 11:57:43 +08:00
ivy-settings.xml LPS-77875 Update cdn url 2018-06-13 14:05:16 -07:00
ivy.xml LPS-74544 SF 2017-12-05 10:08:56 +08:00
ivy.xml.MD5 Simplify build-summary 2018-04-06 15:00:48 -07:00
settings.gradle LRQA-29926 Automatically include all projects with a test.properties 2017-01-24 11:33:08 -08:00
source-formatter.properties LPS-74544 Remove link to file that no longer exists 2017-12-05 09:48:54 +08:00
summary.html Regen summary 2018-04-06 15:02:46 -07:00
summary.xml Regen summary 2018-04-06 15:02:46 -07:00
summary.xsl LPS-29185 2012-08-10 13:14:50 -07:00

README.markdown

Liferay Plugins

The liferay-plugins repository is part of the Liferay Portal project. Liferay Portal is an open source enterprise web platform for building business solutions that deliver immediate results and long-term value. Liferay Portal started out as a personal development project in 2000 and was open sourced in 2001.

To get started, check out the project's community homepage at http://liferay.org!

Most of the plugins found in the liferay-plugins repository can be easily installed on Liferay Portal via Liferay Marketplace. To build one or more of the plugins yourself, read below for details.

Source Code

Liferay's main source code resides in two repositories: liferay-portal and liferay-plugins. Liferay has additional repositories for the following:

Liferay Portal releases are built from the liferay-portal repository and include select plugins from the liferay-plugins repository. You can build Liferay Portal, its plugins, and/or any of the other supporting technologies from their respective repositories.

For more information on building liferay-portal, see the README file in the liferay-portal repository.

Quick Start

In the liferay-plugins repository, plugins are laid out in a software development kit (SDK) -- the Liferay Plugins SDK. All Liferay plugin types, including portlets, themes, layout templates, hooks, and EXT plugins, can be created and maintained in the SDK. Tutorials on the Liferay Developer Network LDN explain how to create, build, and deploy Liferay plugins. But you can conveniently follow the instructions in this section to build and deploy any of the existing SDK plugins right now.

For demonstration purposes, let's pretend your user name is joe and you have a Liferay instance bundled with Apache Tomcat running in your /home/joe/ directory.

  1. Fork the liferay-plugins repository.

  2. Clone your fork of the repository.

  3. Create a build.${username}.properties file in the root directory of your liferay-plugins repository clone. Be sure to replace ${username} with your user name.

     /home/joe/liferay-plugins/build.joe.properties
    

    Note, to determine your user name, execute echo %USERNAME% on Windows or whoami on Unix/Linux.

  4. In your build.${username}.properties file, specify the app.server.parent.dir property set to the parent path of your app server.

     app.server.parent.dir=/home/joe/liferay-portal-6.1.1-ga2
    

    Use your build.${username}.properties file to specify any additional properties you wish to override from the base build.properties file; do not modify the base file.

  5. Navigate to the directory of a plugin (e.g. Sample JSP Portlet) and deploy it using Ant.

     cd /home/joe/liferay-plugins/portlets/sample-jsp-portlet
     ant deploy
    

    The plugin compiles, its WAR file is built to the plugin's dist directory, the WAR file is copied to your Liferay Hot Deploy directory, and the plugin is deployed immediately. It's just that easy!

There are many other options for developing new Liferay plugins using the Plugins SDK. Consult the Liferay Developer Network's Develop section for indispensable explanations, examples, and reference material on the Liferay Plugins SDK and surrounding technologies.

Also, check out Liferay IDE. The Liferay IDE project provides an Eclipse-based Liferay development environment to help you build and maintain Liferay projects easily. The Learning Paths and Tutorials on the Liferay Developer Network show you how to leverage Liferay IDE as you develop on Liferay. LDN also covers developing Liferay plugins using Maven.

Contributing

Liferay welcomes any and all contributions! If you have an idea for a new plugin or a new feature in an existing plugin, and wish to implement it, follow the contribution steps outlined in the CONTRIBUTING guide. It explains how to contribute to Liferay and contains links to additional useful resources.

More Information

For more information about filing bugs, staying updated with Liferay on social media, and other ways to participate, check out the Liferay Community Homepage and consult the README file in the liferay-portal repository.

Liferay Portal Community Edition License

This library, Liferay Portal Community Edition, is free software ("Licensed Software"); you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; including but not limited to, the implied warranty of MERCHANTABILITY, NONINFRINGEMENT, or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA