Ask Questions and Find Answers
Important:
Ask is now read-only. You can review any existing questions and answers, but not add anything new.
But - don't panic! While ask is no more, we've replaced it with discuss - the new Liferay Discussion Forum! Read more here here or just visit the site here:
discuss.liferay.com
RE: 6.2 to DXP 7.1- Maven based Plugin Portlet upgrade using Code Upgrade T
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:
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
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
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?
Best regards.
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.
Powered by Liferay™