Liferay DXP Source Code Access

Please note that an active subscription may be necessary in order to access some repositories and pages mentioned in this article.

This repository replaces source patching mode, which is no longer available for Liferay DXP 7.3+ and Liferay Commerce 3.0+  

Liferay subscribers can now access Liferay DXP source code and fix pack source code in a private GitHub repository.

GET ACCESS

How to gain access to Liferay DXP source code:

source_code_access_add.gif

  1. Navigate to Project Details
    • If you are added to multiple projects, select the desired one from the list
  2. Open the Source Code Access tab
  3. Click on the “+” button
  4. Fill out the requested information:
    • First and last name
    • Email address
    • GitHub username
  5. Submit
  6. The GitHub user will receive an invitation by email to access the Liferay DXP source code repository

You can then continue to add multiple name entries to request on behalf of other project team members.

Due to daily limits on the number of requests, we may not be able to immediately invite every username submitted through the Source Code Access page. Rest assured, we will queue requests and add new users in the following hours or days, as soon as possible.

The access to the Liferay DXP source code repository will be maintained as long as your Liferay DXP Subscription is active. Additionally, if one of the team members changes their GitHub username, they will lose access to the repository.

To change your GitHub username, you will need to first remove the existing username using the steps below, and then request access with the new username.

Misplaced Email Invitation?

If the invitation email was lost or misplaced, the invited user can view and accept the invitation in GitHub: github.com/liferay/liferay-dxp/invitations

REMOVE ACCESS

You can remove team members who are no longer working on the Liferay DXP project with the following steps:

  1. Navigate to Project Details
    • If you are added to multiple projects, select the desired one from the list
  2. Open the Source Code Access tab
  3. Identify the team member to be removed
  4. Expand the team member’s GitHub information
  5. Click Delete

source_code_access_delete.jpg

Note: Invitations remain active for 7 days and can be accepted even if the team member is removed from the Project Details page in Help Center. For example if the GitHub username had a typo, but existed in the system as someone else's account, an unknown person could receive access. To prevent this, the system checks weekly for new collaborators that are not listed on any active projects, to automatically revoke their access.

FIX PACK SOURCE CODE LOOKUP

repo_tags.jpg

The Liferay DXP repository is updated with fix pack tags, which enables you to take a closer look at how code changes with each fix pack. Using these tags you can identify the fix pack changes that are relevant for your project and your custom code, or just view the source code at your existing fix pack baseline.

Important: For Liferay DXP 7.0 and 7.1 source code, fix pack tags are available only starting with these fix pack baselines: 

  • Liferay DXP 7.1 Fix Pack 19
  • Liferay DXP 7.0 Fix Pack 96

BUILD FILES

Liferay DXP provides multiple extension points that allow developers to add functionality and customize their installation. If an extension point does not exist, you can submit a feature request to add the extension point or even the specific functionality.

The use of extension points is the only supported way of customizing Liferay DXP, which is why build files are excluded from the source code repository.

Please contact your Account Executive or Customer Experience Manager for assistance with your custom development or for making a feature request.

PERMISSIONS

Customers who access the Liferay DXP source code repository will have Read level access.

The most relevant allowed actions are:

  • Pull from the repository
  • Fork the repository
  • View published releases

PRIVACY

Our customers’ privacy comes first. When getting access to Liferay DXP source code, you can rest assured that your username, name, email address and any forks remain private. Even though all our customers will get access to the same repository, by default they are not visible to each other.

However, other actions allowed as part of the “Read” permission level will be visible to all other users. In order to maintain privacy, please avoid taking any of the listed actions in the Liferay DXP repository:

  • Edit and delete own comments (1)
  • Open issues (1)
  • Close issues you opened (1)
  • Reopen issues you closed (1)
  • Have an issue assigned to you (1)
  • Send pull requests from forks (2)
  • Submit reviews on pull requests (2)
  • Edit wikis (3)

Please use one of these three official channels to accomplish any of the above tasks, instead:

(1) For Issues and Comments
If you would like to report issues with Liferay software, please contact the Liferay Support team by creating a support ticket in the Help Center. Issues raised in the source code repository will not be answered and will be closed by Liferay.

(2) For Code Contributions
As an open source company, Liferay values and thrives on community contributions. These can be submitted on the public Liferay Portal repository, and if approved will be included in the next release of Liferay DXP. If you would like to contribute to Liferay source code, please follow the community guidelines.

(3) For Wikis
Liferay DXP Documentation and its Knowledge Base are located in the Help Center. Liferay will not use the private repository’s wiki to store documentation. If you would like to suggest edits to one of our articles, or request a new topic to be documented, please use the article Feedback button or contact the Liferay Support team by creating a support ticket in Help Center.

USEFUL RESOURCES

Was this article helpful?
0 out of 0 found this helpful