Once again copy the source zip file to the workspace directory, unzip and rename or soft link as source.ĭrwxr-xr-x 20 4096 09:47 liferay-portal-src-6.0-ee-sp1/ This adds the following to our directory: The bundles name is important here, so don’t get creative. Very similar to the previous step, copy the bundle zip file to the workspace, unzip and either rename or soft link as bundles. Lrwxrwxrwx 1 71 08:17 plugins -> liferay-plugins-sdk-6.0-ee-sp1/ Hopefully it gives you something like this in the workspace directory.ĭrwxr-xr-x 13 4096 12:00 liferay-plugins-sdk-6.0-ee-sp1/ By pointing external configuration at the plugins directory rather than at a specific SDK version, it makes it easier to upgrade your development environmnet later on. Otherwise (and preferably) create a soft link to the SDK directory called plugins. If your operating system does not allow soft links to directories, rename the SDK directory to plugins. ![]() Unzip the file so that there is a directory with the same name eg liferay-plugins-sdk-6.0-ee-sp1. Install Liferay Software Development Kit (SDK)Ĭopy the Liferay SDK zip file eg to the workspace. ![]() Note that the Liferay source, SDK and bundle in the next steps should all be for the same version. For the sake of this article we’ll call the directory workspace. If you have already installed LDS then there is no need to do it again.Ĭreate a new workspace directory for the Liferay project. You can install the LDS to the location of your choice and you can use the same LDS instance to manage multiple Liferay project workspaces, but more on this as we go. Recipe Install Liferay Development Studio This isn’t essential to the set up, but when creating a new development environment we always do this at the same time and there or little additional effort required. The other benefit is that the Tomcat bundle is already assumed and pre-configured for some of the steps below and hence simplifies set up and reduces the work and chances of getting things wrong later. ![]() ![]() A bundle is a pre-packaged Liferay server instance and in our case we tend to use Liferay bundled with Tomcat almost exclusively during development. This does most of the work with respect to building the plugins and the ANT tasks can be used from the command line without requiring the LDS. Liferay Software Development Kit (SDK).This is essentialy the Eclipse IDE plus some Eclipse plug ins to assist Liferay development. There a few slight changes to the setup described in the previous article, but we’ll assume that a Liferay project always requires the following tools: Many of the results of the decisions and best practices can be seen in that post, but there is still plenty that can be covered with respect to setting up a development environment for Liferay plugins. I wrote a post a while back outlining the general set up we use when running our Liferay plugins through Continuous Integration, but it occurred to me that there should be an article that comes before that one which outlines the set up of the development environment.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |