RE: 6.2 to DXP 7.1- Maven based Plugin Portlet upgrade using Code Upgrade T

Gopal Satapathy, modified 6 Years ago. Junior Member Posts: 74 Join Date: 7/28/15 Recent Posts

Hello,

 

I am trying to upgarde the Maven based Plugin Portlet upgrade using Code Upgrade Tool. But i am stuck in the very first step where it requires the path for the project source. i have provided the path for the maven project but still getting "location is not valid".

 

Can someone please help what exact path it expects? Also attaching the pom.xml of the project. Any pointer for this would be of great help.

 

Attachments:

thumbnail
Yanan Yuan, modified 6 Years ago. Junior Member Posts: 89 Join Date: 10/8/11 Recent Posts

Hello,

 

The exact project source should be a Maven Parent path. And according to your attached pom.xml file, the parent project of "holiday-counters-portlet" should be "parent-pom".

 

Could you please enter the parent Maven project path and try agian?

 

Thanks,

Ashley

Gopal Satapathy, modified 6 Years ago. Junior Member Posts: 74 Join Date: 7/28/15 Recent Posts

Hello Yanan Yuan,

 

Thanks for your response.

 

I have tried to give parent maven project path also and still the same result.

Attaching both for reference.

 

Thanks

Gopal

 

thumbnail
Yanan Yuan, modified 6 Years ago. Junior Member Posts: 89 Join Date: 10/8/11 Recent Posts

Hello Gopal,

 

Thanks for the attached projects. I can import both "holiday-counters-portlet" and "parent-poms" projects on my side.

 

Could you try install the latest dev tool and see if that works?

https://sourceforge.net/projects/lportal/files/Liferay%20IDE/3.4.0/LiferayProjectSDKwithDevStudioCommunityEdition-2018.11.4-windows-installer.exe/download

 

Best regards.

Juan Vaca, modified 6 Years ago. New Member Posts: 10 Join Date: 8/23/10 Recent Posts

Hi.  In my case, I had three Ant based projects inside a Liferay SDK plugin directory.   We were upgrading all these projects from Liferay 6.2 to Liferay 7.0.


The upgrade tool did not recognize the portlets project, so I decided not to use it, and I did a manual migration of all our eight (8) portlets.
I started creating the Liferay SDK project, and I continue creating the theme project, the layout page project, and finally the portlet project. These projects are Gradle based now.


Then I began to migrate every portlet to OSGI.  I used this documentation to convert the portlet descriptor to OSGi properties:

Portlet Descriptor to OSGi Service Property Map


Eventually, I was able to finish the migration in a relatively easy process.


You can try to do the same.  Of course, if you have the time.