Working with Liferay’s Developer Tools
If you’re anything like Liferay Portal’s developers, you don’t want to be forced to work with one development technology. Our developers build Liferay with the tools they prefer. That’s why we strive to provide you with as much flexibility as possible. You can develop your Liferay-based portal with tools ranging in complexity from IDEs like Eclipse, Netbeans, or IntelliJ Idea, to text editors like Notepad, Vim, or Emacs. You can write your persistence layer directly using SQL and JDBC, or use advanced object-relational mapping libraries like Hibernate or iBATIS. You get the idea.
In this chapter, we’ll explain how to set up a streamlined development environment specifically designed for developing your Liferay Portal. Then we’ll consider how to develop plugins with other tools. We’ll cover the following topics along the way:
- Developing Apps with Liferay IDE
- Leveraging the Plugins SDK
- Developing Plugins Using Maven
Liferay’s tool-agnosticism is great for experienced developers who understand the strengths and weaknesses of different development technologies; it can be overwhelming for newcomers, though. So we removed some of the options, narrowing down your choices and forcing you to use a tool we like, right? No! We actually added to the list of technologies you can use by developing specific tools that soften the learning curve for Liferay plugin development, and providing ways for you to use alternative tools. The most significant Liferay-specific tool is Liferay IDE, a fully featured Integrated Development Environment (IDE) based on Eclipse. There’s also the Plugins Software Development Kit (SDK), which is based on Apache Ant and can be used with any editor or Integrated Development Environment you’d like. If you’d like, you can also use Apache Maven archetypes; there are plenty of Liferay archetypes you can use to develop your plugins.
First let’s consider the most robust tool for Liferay development, Liferay IDE.