-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Discarded
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: ~ [Archived] Themes Infrastructure
-
Labels:None
In the past, exported content (lar) contained a necessary field build-number="xxxx" that was used to verify if the content could be imported.
As of Liferay Portal GA3+ and Liferay DE fixpack-1, this is no longer necessary and the import process does not fail if the build-numbers don't match.
In order to achieve maximum compatibility with Liferay DE versions, the themes should be able to specify a particular build-number that, when present, should override that found in the resources-importer/private/manifest.xml file.
For example, this could be used as follows (only an idea)
- Open liferay-plugin-package.properties file
- Add an override-content-build-number=7010 line
- On build time, the string build-number="7001" will be replaced with build-number="7010" in the resources-importer/private/manifest.xml file before generating the private.lar file