Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8456819
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T12:38:48+00:00 2026-06-10T12:38:48+00:00

I’d like to ask you for best practices with developing with Liferay SDK. I

  • 0

I’d like to ask you for best practices with developing with Liferay SDK.
I have the SDK downloaded, I have Eclipse ready, it works, I can create new portlets and run local Liferay instance to test it.

Here is my situation – all the source code I have is in the Eclipse workspace, currently it is only portlets what I’m working on.

Liferay SDK I have in completely different location than workspace. Let’s say ~/dev/liferay_sdk.
Eclipse workspace is located in ~/workspace.

At the beggining, it was not working like that. Eclipse from some reason can’t find or use Liferay SDK. When I changed “Project validation” in Eclipse/Liferay configuration to “Ignore” the “Liferay Plugin SDK is not valid”, it started to work without problems.

Next problem happend when it comes to need to build a WAR for example.
In the portlet directory in the workspace is present “build.xml” file. But inside it refers to another xml file, which should be located one directory up, and this one refers to more thing in relatively location and so on.

In short, it assumes that you have the portlets etc, inside the Liferay SDK.
Like “~/dev/liferay_sdk/portlets”.

My question is, Am I wrong completely, or could you suggest me the best practices with this?

I don’t want to mix SDK and the code, it sounds wrong to me.

Thanks for help!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T12:38:49+00:00Added an answer on June 10, 2026 at 12:38 pm

    I think, the best practice is still when your portlet projects are located inside the Liferay Plugins SDK directory. That way you can take all the advantages of the Liferay IDE plugin for Eclipse, for example. Because as far as I understand Liferay IDE will not allowed you to have portlet projects in another location. It’s pretty easy to import projects to Eclipse from inside the Liferay SDK directory, and that’s not problem.

    But I also faced the same sort of problem when tried to save portlet project to the Git repository. Possible solutions with symbolic links didn’t work correctly on every system. Thus I slightly modified the build.xml file to be able to run ant tasks from any directory. For portlets it was something like that:

    <project name="your-portlet" basedir="." default="deploy">
        <property file="build.properties" />
    
        <property name="project.dir" value="${liferay.sdk.home}" />
    
        <import file="${project.dir}/build-common-plugin.xml" />
    </project>
    

    Notice that you should define property “liferay.sdk.home” in build.properties and it should be path to the Liferay Plugins SDK.

    As for other types of Liferay plugins (themes, hooks, etc.) you should import another build file for building that type of plugin. For example, for themes it will be:

    <import file="${project.dir}/themes/build-common-theme.xml" />
    

    Hope you’ll get the idea. 🙂 But think twice before doing something like that.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a string like this: La Torre Eiffel paragonata all&#8217;Everest What PHP function
I have a jquery bug and I've been looking for hours now, I can't
I have two tables with like below codes: Table: Accounts id | username |
I have a .ini file as follows: [playlist] numberofentries=2 File1=http://87.230.82.17:80 Title1=(#1 - 365/1400) Example
I would like to count the length of a string with PHP. The string
For some reason, after submitting a string like this Jack’s Spindle from a text
link Im having trouble converting the html entites into html characters, (&# 8217;) i
I have just tried to save a simple *.rtf file with some websites and
Basically, what I'm trying to create is a page of div tags, each has
I've got a string that has curly quotes in it. I'd like to replace

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.