RE: Is this the best way to provide a customized community portal?

Olaf Kock, modified 2 Years ago. New Member Posts: 4 Join Date: 9/18/23 Recent Posts

Hey there,

I plan to set up and operate a portal for a small community web-site, so i checked out liferay as it has all required features and seems to be extendable in future.

I have some expierence in Java / Web-Development, so I forked the portal, made some customizations and build a release using the provided ANT scripts.
I prefer this approach (instead of overriding the modules), because i can see all changes and conflicts in the Git upstream project.

But there are some differences in my realease file compared to the downloaded release file (e.g. apps are provided in the modules directory as single JARs instead as compressed marketplace LPKGs).

So my questions are:
Is my aproach of building the portal and using the bundle of the dist-task the correct way?
Is it secure to do so or are there some development tweaks compared to the official release?

Thanks for any information!
​​​​​​​Timo

​​​​

 

thumbnail
Jamie Sammons, modified 1 Year ago. Liferay Legend Posts: 6441 Join Date: 9/23/08 Recent Posts

No, in the interest of keeping a maintainable installations, you should strictly use the documented extension points (modules, or better Client Extensions) instead of preparing elaborated three-way-merges to incorporate any and all future changes to the Liferay core.