ledasfen.blogg.se

Liferay portal bundle directory
Liferay portal bundle directory












liferay portal bundle directory
  1. #Liferay portal bundle directory professional
  2. #Liferay portal bundle directory download

  • Now for the real trick, liferay 4.2 has a small bug when changing the context to something other than the ROOT.
  • Under the WEB-INF folder, create a 'classes' folder, in this folder create a file called 'portal-ext.properties', and in this file place the following (note that users may of course change the portal.ctx and/or the lucene and jackrabbit directory depending on later configurations):.
  • In order to keep the ROOT folder, extract the contents of the war into a folder, call it 'myportal' for instance.
  • #Liferay portal bundle directory download

    Download the additional file called Liferay Portal 4.2.1 Dependencies, and unzip it to shared/lib.

    #Liferay portal bundle directory professional

    Download the non-bundled liferay war (Liferay Portal Professional 4.2.1 WAR) from Liferay.Typically, Liferay's installation removes the ROOT folder from the server, to avoid this situation, please stick to the following steps closely. If the user already has a tomcat server on hand and does not particularly feel like deploying another one, the second option would be to download "liferay war". During this workflow, liferay-npm-bundler calls all the configured plugins so they can perform transformations on the npm packages (for instance, modifying their package.json files or deleting or moving files).There are several ways in which an application can be set up within Liferay, the first one being to simply go to Liferay and download the pre-bundled liferay tomcat bundle (other app server bundles are also available but experiences indicate that other ones might be trickier to begin with as the configuration is usually more lengthy), however, this option is not ideal if the user already have an existing tomcat server. The only difference between the pre-process and post-process steps are when they are run (before or after Babel is run, respectively). Post-process the npm package with any configured plugins. Run Babel with configured plugins for each. Pre-process the npm package with any configured plugins.ĭ. To determine what is copied, the bundler invokes a plugin to filter the package file list.Ĭ. Note that the bundler stores packages in a plain version format, rather than the standard node_modules tree format. Copy the npm package to the output folder and prefix the bundle’s name to it. Post-process the project package with any configured plugins.Ī. Pre-process the project’s package with any configured plugins.Ĭ. npmbundlerrc configuration, through the rules.ī. Traverse the project’s dependency tree to determine its dependencies.Ī. The liferay-npm-bundler uses the process below to create the OSGi bundle:Ĭopy the project’s package.json file to the output directory. You can learn more about the build folder’s structure in OSGi Bundles and npm Package Structure reference. The liferay-npm-bundler takes a widget project and outputs its files (including npm packages) to a build folder, so the standard widget build (Gradle) can produce an OSGi bundle.

    liferay portal bundle directory

    How the Liferay npm Bundler Works Internally ¶

    liferay portal bundle directory

  • Understanding the npmbundlerrc Structure.
  • Understanding Bundler Configuration Presets.
  • How JavaScript Modules are Formatted for AMD.
  • How AMD Loader Configuration is Exported.
  • Understanding the Liferay npm Bundler Loader.













  • Liferay portal bundle directory