Details

      Description

      Currently when implementing a customized version of an out of the box component it is necessary to create a separate osgi configuration file to blacklist the out of the box component to ensure that it is not active.

      To make this process simpler the Blacklist API could be made accessible so that out of the box components can be blacklisted from within a project's code. Removing the need for a separate OSGI configuration file that would have to be maintained as well.

        Attachments

          Activity

            People

            • Assignee:
              support-lep@liferay.com SE Support
              Reporter:
              nathan.roberts Nathan Roberts
            • Votes:
              5 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Packages

                Version Package