liferay-plugins | plugins repository is part of the Liferay Portal | Runtime Evironment library

by liferay Java Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | liferay-plugins Summary

liferay-plugins is a Java library typically used in Server, Runtime Evironment, React, Nodejs, Bootstrap, Framework applications. liferay-plugins has no bugs, it has no vulnerabilities, it has build file available and it has low support. However liferay-plugins has a Non-SPDX License. You can download it from GitHub, Maven.

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.

Support

Quality

Security

License

Reuse

Support

liferay-plugins has a low active ecosystem.

It has 513 star(s) with 2115 fork(s). There are 112 watchers for this library.

It had no major release in the last 6 months.

liferay-plugins has no issues reported. There are 9 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of liferay-plugins is current.

Quality

liferay-plugins has no bugs reported.

Security

liferay-plugins has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

liferay-plugins has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

liferay-plugins releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed liferay-plugins and discovered the below as its top functions. This is intended to give you an instant insight into liferay-plugins implemented functionality, and help decide if they suit your requirements.

Creates the auto scaling group
Checks if the specified auto - scaling group is enabled
Get image id by name
Method to get list of instanceStateObjects of instanceStateObjects
Returns an XML representation of the Entry
Updates the entry
Returns a representation of this entry in XML format
Updates an Entry
Updates the microblogs entry
Converts MicroblogsEntry to MicroblogsEntry
Update status
Returns the XML representation of this model
Returns a XML representation of this sample
Returns a representation of this model
Returns an XML representation of this model
Update the JIRActions
Returns a raw XML representation of this model
Returns the MicroblogEntry as XML
Updates the TasksEntry
Updates the webEx site
Update a Foo object
Update SampleLARBooking
Returns the Tasks entry in XML format
Returns this column as an XML String
Update the JIRAIssueImpl
Updates the webEx account

Get all kandi verified functions for this library.

liferay-plugins Key Features

No Key Features are available at this moment for liferay-plugins.

liferay-plugins Examples and Code Snippets

No Code Snippets are available at this moment for liferay-plugins.

Community Discussions

Trending Discussions on liferay-plugins

Error when adding new table on service.xml - Liferay 6.2

How to deploy a theme in liferay?

QUESTION

Error when adding new table on service.xml - Liferay 6.2

Asked 2020-Oct-28 at 08:32

I'm using liferay 6.2 and I want to add a new table on service.xml.

The new entry on service.xml is:

...

ANSWER

Answered 2020-Oct-28 at 08:32

I hardly remember that there was an issue with the keyword "error" in table or column names. The service builder once greped for this keyword. You might give it a try to not use the word "error" in your column definition.

Source https://stackoverflow.com/questions/64559029

QUESTION

How to deploy a theme in liferay?

Asked 2017-Dec-13 at 15:28

I am trying to check if my theme project is running with the different version.

I downloaded all the versions that i need (6.2: ga1,ga2,ga3,ga4,ga5,ga6) and I configured the servers and the sdk for each server.

I did (Import -> liferay projects from plugins SDK). In the import window I got a message:

SDK version and Liferay runtime version may not be compatible.

I imported the theme and I tried to deploy it (liferay -> deploy) but I got an error:

Error running SDK command deploy java.lang.NullPointerException

I am using Eclipse Kepler-4.3 and Liferay 6.2.

Error Description

I tried Run As-> Ant Build

I got this error:

Buildfile: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\material-admin\Material-admin-theme\build.xml

BUILD FAILED D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\material-admin\Material-admin-theme\build.xml:5: Cannot find D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\material-admin\build-common-theme.xml imported from D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\material-admin\Material-admin-theme\build.xml

Total time: 1 second

Update 1:

I tried to use ant deploy but I got an error:

compile: D:\FormationJEE\Liferay\Liferay-6.2.0-ce-ga1\liferay-plugins-sdk-6.2.0-ce-ga1-20131101192857659\bundles \tomcat-7.0.42\lib\ext does not exist. at org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractFileSet.java:495) at org.apache.tools.ant.types.FileSet.iterator(FileSet.java:70) at org.apache.tools.ant.types.resources.Union.getAllResources(Union.java:148) at org.apache.tools.ant.types.resources.Union.getCollection(Union.java:108) at org.apache.tools.ant.types.resources.BaseResourceCollectionContainer.cacheCollection(BaseResourc eCollectionContainer.java:263) at org.apache.tools.ant.types.resources.BaseResourceCollectionContainer.iterator(BaseResourceCollec tionContainer.java:142) at org.apache.tools.ant.types.Path.iterator(Path.java:709) at org.apache.tools.ant.types.Path.iterator(Path.java:702) at org.apache.tools.ant.types.resources.Union.getAllResources(Union.java:148) at org.apache.tools.ant.types.resources.Union.getAllToStrings(Union.java:128) at org.apache.tools.ant.types.resources.Union.list(Union.java:87) at org.apache.tools.ant.types.Path.list(Path.java:378) at org.apache.tools.ant.types.Path.addExisting(Path.java:330) at org.apache.tools.ant.types.Path.addExisting(Path.java:318) at org.apache.tools.ant.types.Path.concatSpecialPath(Path.java:569) at org.apache.tools.ant.types.Path.concatSystemClasspath(Path.java:529) at org.apache.tools.ant.AntClassLoader.setClassPath(AntClassLoader.java:363) at org.apache.tools.ant.AntClassLoader.(AntClassLoader.java:277) at org.apache.tools.ant.AntClassLoader.(AntClassLoader.java:298) at org.apache.tools.ant.AntClassLoader.newAntClassLoader(AntClassLoader.java:1562) at org.apache.tools.ant.Project.createClassLoader(Project.java:345) at org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:130) at org.apache.tools.ant.taskdefs.Java.run(Java.java:834) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:228) at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:137) at org.apache.tools.ant.taskdefs.Java.execute(Java.java:110) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroInstance.java:402) at net.sf.antcontrib.logic.ForTask.doSequentialIteration(ForTask.java:259) at net.sf.antcontrib.logic.ForTask.doToken(ForTask.java:268) at net.sf.antcontrib.logic.ForTask.doTheTasks(ForTask.java:324) at net.sf.antcontrib.logic.ForTask.execute(ForTask.java:244) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68) at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:155) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293) at jdk.internal.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl. java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:564) at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106) at org.apache.tools.ant.Task.perform(Task.java:348) at org.apache.tools.ant.Target.execute(Target.java:435) at org.apache.tools.ant.Target.performTasks(Target.java:456) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1405) at org.apache.tools.ant.Project.executeTarget(Project.java:1376) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) at org.apache.tools.ant.Project.executeTargets(Project.java:1260) at org.apache.tools.ant.Main.runBuild(Main.java:857) at org.apache.tools.ant.Main.startAnt(Main.java:236) at org.apache.tools.ant.launch.Launcher.run(Launcher.java:287) at org.apache.tools.ant.launch.Launcher.main(Launcher.java:113) Java Result: -1

BUILD FAILED

How to deploy a theme in liferay using the IDE and the Ant line command?

Update 2:

I moved the directory higher and I imported the project.

First I tested the GA1 version and I did (liferay -> deploy) it worked. Then when I tried to import the project for GA2, i got a message:

SDK version and Liferay runtime version may not be compatible.

The following picture shows the details:

In the Liferay target runtime, if I select a configuration for the SDK: GA2, GA3, GA4, GA5, GA6.

For example:

Liferay Plugins SDK: liferay-plugins-sdk-6.2 (GA2)
Liferay target runtime: Liferay v6.2 CE (GA2) (Tomcat 7)

Only if I select Liferay v6.2 SE (GA1) (Tomcat 7), The message gone.

If I select a configuration like this (GA2-GA2), ... ,(GA6-GA6) the message appeared.

If I select a configuration like this (GA1-GA1), (GA2-GA1), ... ,(GA6-GA1) the message gone.

For (GA1-GA1) he has no problems.

After I imported the project, I have this error message:

[Console output redirected to file:D:\FormationJEE\Liferay\workspace.metadata.plugins\com.liferay.ide.sdk.core\sdk.log] Buildfile: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\Material-admin-theme\build.xml [ivy:resolve] :: Apache Ivy 2.3.0 - 20130110142753 :: http://ant.apache.org/ivy/ :: [ivy:resolve] :: loading settings :: file = D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\ivy-settings.xml [ivy:resolve] :: problems summary :: [ivy:resolve] :::: WARNINGS [ivy:resolve] module not found: biz.aQute#bnd;2.3.0 [ivy:resolve] ==== asu-gibson: tried [ivy:resolve]
https://gibson.asu.edu/maven/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
https://gibson.asu.edu/maven/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== jboss-nexus: tried [ivy:resolve]
https://repository.jboss.org/nexus/content/repositories/releases/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
https://repository.jboss.org/nexus/content/repositories/releases/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== jboss-thirdparty: tried [ivy:resolve]
https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== maven2: tried [ivy:resolve]
http://repo1.maven.org/maven2/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
http://repo1.maven.org/maven2/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== ow2-public: tried [ivy:resolve]
http://repository.ow2.org/nexus/content/repositories/public/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
http://repository.ow2.org/nexus/content/repositories/public/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== primefaces: tried [ivy:resolve]
http://repository.primefaces.org/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
http://repository.primefaces.org/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== liferay-public: tried [ivy:resolve]
https://repository.liferay.com/nexus/content/groups/public/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
https://repository.liferay.com/nexus/content/groups/public/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== pentaho: tried [ivy:resolve]
http://repository.pentaho.org/artifactory/repo/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
http://repository.pentaho.org/artifactory/repo/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] ==== soapui: tried [ivy:resolve]
http://www.soapui.org/repository/maven2/biz/aQute/bnd/2.3.0/bnd-2.3.0.pom [ivy:resolve] -- artifact biz.aQute#bnd;2.3.0!bnd.jar: [ivy:resolve]
http://www.soapui.org/repository/maven2/biz/aQute/bnd/2.3.0/bnd-2.3.0.jar [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: [ivy:resolve] :: UNRESOLVED DEPENDENCIES :: [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: [ivy:resolve] :: biz.aQute#bnd;2.3.0: not found [ivy:resolve] :::::::::::::::::::::::::::::::::::::::::::::: [ivy:resolve] [ivy:resolve] [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD FAILED D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\Material-admin-theme\build.xml:5: The following error occurred while executing this line: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\themes\build-common-theme.xml:5: The following error occurred while executing this line: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\build-common-plugin.xml:5: The following error occurred while executing this line: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\build-common.xml:47: The following error occurred while executing this line: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\build-common-ivy.xml:34: The following error occurred while executing this line: D:\FormationJEE\Liferay\Liferay-6.2-ce-ga2\liferay-plugins-sdk-6.2-ce-ga2-20140319114139101\liferay-plugins-sdk-6.2\build-common-ivy.xml:50: impossible to resolve dependencies: resolve failed - see output for details

Total time: 11 seconds

Update 3:

I had a compatibility problem with SDK version and Liferay runtime.

I tried to create build.yoursystemusername.properties file inside the plugin sdk.

These two lines deleted several errors for some version:

...

ANSWER

Answered 2017-Oct-24 at 06:32

You have a weird collection of versions there. Do not use all of GA1-6, rather opt for one (the latest).

And on the rest: You're building some theme and the build process is missing a file. Note that your theme's build file is \liferay-plugins-sdk-6.2\themes\material-admin\Material-admin-theme\build.xml. Open that file and check what it includes: You'll find ../build-common-theme.xml, which is exactly the missing file. Search for the file, and you'll find it one directory further up. This will tell you that Plugin SDK has not been built for themes being stored two levels down from the SDK's root directory. I'd recommend to move your theme one level up, but you might have luck with changing the build file include in your theme's build.xml

As of the NullpointerException: Not enough information here. But when your theme doesn't build at all, no wonder that something isn't working as expected.

Source https://stackoverflow.com/questions/46890995

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install liferay-plugins

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. 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.
Fork the liferay-plugins repository.
Clone your fork of the repository.
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.
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.
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!

Support

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.

Find more information at: