Hello Fellow Forums Followers,

I have a simple question.

What is the recommended WAR file naming convention for plugins to support Liferay Portal 6.1 and 6.2 ?

The Liferay Portal 6.1 and 6.2 Developer guides at

* https://www.liferay.com/documentation/liferay-portal/6.1/development/-/ai/lp-6-1-dgen10-marketplace-basics-0
* https://www.liferay.com/documentation/liferay-portal/6.2/development/-/ai/marketplace-basics-liferay-portal-6-2-dev-guide-11-en

state the following regarding WAR file names,



I want to build and deploy the same functionality to both platforms, hence want to retain the same version number (e.g.. 1.0.4).

However, the Marketplace uploader checks and verifies names according to the Marketplace developer guide and does not allow a naming convention such as

plugin_type -A.B.C.D-LPVERSION.war

or

plugin_type -LPVERSION-A.B.C.D.war

eg.

my-app-1.0.4.1-lp-6.1.x.war
my-app-1.0.4.1-lp-6.2.x.war


What is the recommended approach for building and naming plugins (eg. hook plugins) to support Liferay Portal 6.1 and 6.2 ?

Due to core JSP changes between LP 6.1 and 6.2 I cannot simply build one plugin and target 2 platforms. I must maintain 2 plugins, one per platform.

Have I missed something in the docs ?


Thanks,

Tim

Hello Forum,

to partially answer my own query, the default solution is to use the file naming conventions of the Liferay (Ant) Plugins SDK which (by default) packages plugins with the expected file naming convention of "pluginname-plugintype.A.B.C.D.war".

I still seek a supported file naming convention for Liferay Marketplace Apps (plugins) which supports Liferay Portal version number and plugin version number.


- Tim

G'day Tim, glad to hear you found a workaround! Yes, the required naming of plugins (from the Developer Guide) is a little... draconian, but it only defines one place for an obvious version. I guess the good news is that I don't believe the version in the filename is actually used or parsed or relied upon in any way, so it could be relaxed in the future. But for now, there is no best practice for including the LR version in the filename of your plugins, although it would make a lot of sense to do so when you build plugins for multiple LR versions. So I can suggest something like foo620-portlet.1.0.0.0.war and foo6210-portlet-1.0.0.0.war. (for version 1.0 of your plugin that supports 6.2.0 (CE GA1) and 6.2.10 (EE GA1)).