Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-94607

As a workspace user, I would like to be able express my 'providedModules' dependencies close the modules that depend on them

    Details

      Description

      Right now if two portlets lets say
      foo-portlet
      bar-portlet
      Both want to depend on guava in their osgi bundles. They can either use 'compileInclude' in the build.gradle but that means the dependency isn't shared. IF they want to'share' the dependency as a peer osgi bundle then they have to.

      In root workspace build.gradle add guava as a dependency on the 'providedModules' configuration and then also in each respective project they have to put the same guava as a compileOnly dependency.

      It would be nice if these 'providedModules' dependencies could be expressed by the actual module that needs it in their build.gradle instead of in the root. and then the foo-portlet and bar-portlet would only need to add 'provideModules' in their dependencies and wouldn't have to also repeat themselves with a a'compileOnly' dependency. In other words in a module project a 'providedModules' dependency would be the same as a 'compileOnly' dependency (added on the project classpath) as well added into the 'liferay/osgi/modules' folder during initBundle task.

        Attachments

          Activity

            People

            Assignee:
            support-lep@liferay.com SE Support
            Reporter:
            gregory.amerson Gregory Amerson
            Recent user:
            Kiyoshi Lee
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:

                Packages

                Version Package