Uploaded image for project: 'PUBLIC - Liferay IDE'
  1. PUBLIC - Liferay IDE
  2. IDE-3697

Differences between versions in com.liferay.portal.kernel in the autogenerated build.gradle between different project types

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.2
    • Fix Version/s: None
    • Component/s: Modules
    • Environment:
      Liferay Developer Studio Version: 3.1.2.201709011126-ga3

      Description

      After creating a service-service and a service-api, there is a difference between versions in com.liferay.portal.kernel the pre-built build.gradle.

      When examining build.gradle, we can see that com.liferay.portal.kernel in service-api has a version of 2.0.0, and com.liferay.portal.kernel in service-service has a version of 2.6.0.

      compileOnly group: "biz.aQute.bnd", name: "biz.aQute.bndlib", version: "3.1.0"
      	compileOnly group: "com.liferay", name: "com.liferay.osgi.util", version: "3.0.0"
      	compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "2.0.0"
      	compileOnly group: "org.osgi", name: "org.osgi.core", version: "6.0.0"
      }
      
      dependencies {
      	compileOnly group: "biz.aQute.bnd", name: "biz.aQute.bndlib", version: "3.1.0"
      	compileOnly group: "com.liferay", name: "com.liferay.osgi.util", version: "3.0.0"
      	compileOnly group: "com.liferay", name: "com.liferay.portal.spring.extender", version: "2.0.0"
      	compileOnly group: "com.liferay.portal", name: "com.liferay.portal.kernel", version: "2.6.0"
      	compileOnly project(":aSample-api")
      }

      I understand that this is a minimum version requirement (e.g. (2.0.0,3.0.0] or (2.6.0,3.0.0]), and that the build.gradle is auto-generated as a suggestion and allows a developer to configure to the version of their liking, but isn't it better to set it at the same version?

      I'm asking because there could be interface changes in a higher version compared to a lower version, and if one project type has the lower version, it might cause an unnecessary extra step to change the version and refresh the gradle project. Wouldn't it be better to make sure that all project types use the same version of the minimum version of the component in the auto-generated build.gradle?

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                1 year, 6 weeks, 3 days ago

                Packages

                Version Package