Package range version definition

RE: Package range version definition

2018-09-19T16:41:29Z

That is a good question. In theory it should not change between GA releases. But as those versions (7.0, 7.1, ...) are more of marketing versions than semantically versioned product releases, the reality is sometime bundles get updated in between GA releases. So I'd say you should treat next GA release more or less as next minor version update which means assume bundles and packages will be updated.

RE: Package range version definition

2018-09-19T13:11:32Z

Thanks Milen, if I implement a module for 7.0.5-GA6 platform I hope that the same module will work on 7.0.6-GA7? or the minor version

of the provider type package could be change?

RE: Package range version definition

2018-09-19T12:28:37Z

Typically the range is created by Bnd. It inspects the code and figures out what packages give package uses. Then it finds the packages on the classpath and tries to determine what is the version in use. If the package is versioned the range is generated. Depending on whether the package contains only consumer types (default) or also provider types it will either create the upper limit to be next major or next minor version. The idea here is that providers may brake on minor changes while consumers should never do so.

Package range version definition

2018-09-19T08:13:07Z

Hi all. I opened MANIFEST.MF file inside the portal-kernel.jar. I found this declaration:

[...]
Import-Package: com.liferay.announcements.kernel.exception;version="[1.0,2)",com.liferay.announcements.kernel.model;
version="[1.0,1.1)",com.liferay.asset.kernel;version="[1.1,2)"[...]

How is the range version created? Why is defined the range version for the package "com.liferay.announcements.kernel.model"? Why the upper limit is 1.1 and not 2?

Thanks in advance.

Enrico