In order for a plugin to affect the portal it must be deployed to it. As you develop plugins you’ll want to test them on a portal. Commonly, developers test their plugins on a portal instance on their machine. Deploying to a local instance is non-restrictive and easy to do. Eventually, however, you’ll need to deploy your plugins to remote test servers and, finally, to production servers. No matter what stage of development you’re in, it’s important for you and your portal administrators to know the plugin deployment options available. This section of tutorials explains the deployment options and how they work.

Deploying Plugins to a Local Portal Instance

Liferay IDE provides multiple options for deploying plugins: you can drag and drop your project onto the server or right click the server and select Add and Remove…. It’s almost as easy using an...

Read More

Using Liferay IDE’s Remote Server Adapter

The Remote Server Adapter lets you deploy local plugin projects to remote servers. You can use it to deploy apps you’re developing to a test server for your QA team or to a beta server for your...

Read More

Hot Deploy Versus Auto Deploy

As you develop plugins you’ll want to deploy them to your test servers and as you finish developing plugins you’ll want to deploy them to your production servers. There are hot deploy and auto...

Read More
0 (0 Votes)
Building Liferay Maven Artifacts from Source Previous