PUBLIC - Liferay Portal Community Edition

Can't upload in marketplace: Please define a compatible Liferay version in liferay-plugin-package.properties

Details

  • Similar Issues:
    Show 5 results 

Description

I would want to create an app in liferay.com marketplace with the appmanager.
My app is a single war and contains liferay-plugin-package.properties.

But when I upload the war file, it is not accepted and an error is displayed "Please define a compatible Liferay version in liferay-plugin-package.properties".
Whatever liferay versions I try in liferay-plugin-package.properties, it is always the same.

The war seems correct to me. I have attached it in the issue (liferay-javamelody.war).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
evernat added a comment -

I have found the cause.
The war file to upload should end with "-portlet" or "-web" or "-portlet" or others like that.
For example, it should be "liferay-javamelody-hook.war" and not "liferay-javamelody.war".

This requirement is perhaps obvious, but anyway this issue is now that the error message is incorrect in this case.

In fact, it should not be "Please define a compatible Liferay version in liferay-plugin-package.properties"
but the message should be that the file must be named for example "abc-portlet.war", "abc-web.war" or "abc-hook.war"

Show
evernat added a comment - I have found the cause. The war file to upload should end with "-portlet" or "-web" or "-portlet" or others like that. For example, it should be "liferay-javamelody-hook.war" and not "liferay-javamelody.war". This requirement is perhaps obvious, but anyway this issue is now that the error message is incorrect in this case. In fact, it should not be "Please define a compatible Liferay version in liferay-plugin-package.properties" but the message should be that the file must be named for example "abc-portlet.war", "abc-web.war" or "abc-hook.war"
Hide
Permalink
Eva Sciacca added a comment -

I also have the same problem. I have added the liferay-plugin-package.properties and named my .war portlet as ProjectName-portlet.war
Could you please advise me if you have solved this issue?

Show
Eva Sciacca added a comment - I also have the same problem. I have added the liferay-plugin-package.properties and named my .war portlet as ProjectName-portlet.war Could you please advise me if you have solved this issue?
Hide
Permalink
evernat added a comment -

see the comment above

Show
evernat added a comment - see the comment above
Hide
Permalink
Eva Sciacca added a comment -

Yes, as I have already written I have added to my project the file named liferay-plugin-package.properties containing the following row:
liferay-versions=6.1.0
into the dir:
/WEB-INF
Then I named the .war file as ProjectName-portlet.war and that not worked giving again the same error:
Please define a compatible Liferay version in liferay-plugin-package.properties.
Do you have any other suggestions on what can be the cause?
Thank you in advance.

Show
Eva Sciacca added a comment - Yes, as I have already written I have added to my project the file named liferay-plugin-package.properties containing the following row: liferay-versions=6.1.0 into the dir: /WEB-INF Then I named the .war file as ProjectName-portlet.war and that not worked giving again the same error: Please define a compatible Liferay version in liferay-plugin-package.properties. Do you have any other suggestions on what can be the cause? Thank you in advance.
Hide
Permalink
Mika Koivisto added a comment -

Ryan can you check this issue?

Show
Mika Koivisto added a comment - Ryan can you check this issue?
Hide
Permalink
Ryan Park added a comment - - edited

Edit:

Just some clarifications, I've checked and there are 2 versions accepted by the Marketplace and they are 6.1.1 and 6.1.20.

I've will also check to see what is happening with the documentation for Marketplace. I do believe we have planned something extra for Marketplace.

Show
Ryan Park added a comment - - edited Edit: Just some clarifications, I've checked and there are 2 versions accepted by the Marketplace and they are 6.1.1 and 6.1.20. I've will also check to see what is happening with the documentation for Marketplace. I do believe we have planned something extra for Marketplace.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    21 weeks, 4 days ago