Manish Jha 6 Years Ago Thanks for introduction. I am waiting for next blog of the series.Should I start clone the .gradle from https://github.com/liferay/liferay-portal/tree/master/.gradle/caches/modules-2/files-2.1 ? Please sign in to reply. Reply as... Cancel Minhchau Dang Manish Jha 6 Years Ago - Edited Unlike SVN, you won't be able to grab specific folders with Git, so you'll be cloning the root of the repository. I believe SSH is faster than HTTPS, so unless you have a company firewall that only allows HTTPS, you should use SSH.git clone git@github.com:liferay/liferay-portal.git Please sign in to reply. Reply as... Cancel
Minhchau Dang Manish Jha 6 Years Ago - Edited Unlike SVN, you won't be able to grab specific folders with Git, so you'll be cloning the root of the repository. I believe SSH is faster than HTTPS, so unless you have a company firewall that only allows HTTPS, you should use SSH.git clone git@github.com:liferay/liferay-portal.git Please sign in to reply. Reply as... Cancel
Antonio Musarra 6 Years Ago Can I contribute to one module? For example, I would like to contribute to the *com-liferay-portal-remote module*, in this case should I fork this module and then pull-request or make the fork of liferay-portal? Please sign in to reply. Reply as... Cancel
Sushil Patidar 6 Years Ago Liferay source size in repo is growing day by day. So when we clone it fetches all its history due to which it clone a big size repo. Is there a way we can clone only with latest history.It would be easier to contribute for community members. Waiting for such an blog that solves this concern.Thanks Please sign in to reply. Reply as... Cancel Minhchau Dang Sushil Patidar 6 Years Ago - Edited Well, "git clone" allows for a "depth" parameter that lets you specify how many commits you want to retain, and a "shallow-since" that lets you specify a time range.https://git-scm.com/docs/git-cloneYou would also want to exclude tags if you want a small repository (not sure if that's implicit when it's a single branch clone; the documentation makes it sound like it needs to be explicit).git clone --depth=1 --branch master --no-tags git@github.com:liferay/liferay-portal.gitI tested from home, and the clone takes about 6 minutes and the resulting repository uses 4 GB, with 2 GB inside of the .git folder.However, a shallow clone means that you have to use the GitHub UI in order to navigate history, because your local copy has no history at all. So, while the resulting file size is smaller and it does take less time to clone, the tedium of not being able to use local tooling makes it less desirable.But maybe that's just my biased opinion, since my day to day work requires navigating the repository history. Please sign in to reply. Reply as... Cancel Sushil Patidar Minhchau Dang 6 Years Ago Thanksit's a great help. After liferay source build is complete. if it is needed to build a particular module only let say shopping module. Is it feasible?Reragds Please sign in to reply. Reply as... Cancel Minhchau Dang Sushil Patidar 6 Years Ago Yes. If you've built the whole thing from source, you can deploy individual modules after that. The second blog in this series has an example where it redeploys the dynamic-data-mapping-data-provider-instance module.https://web.liferay.com/web/minhchau.dang/blog/-/blogs/troubleshooting-liferay-from-source#step-6-test-your-changes-part-1 Please sign in to reply. Reply as... Cancel
Minhchau Dang Sushil Patidar 6 Years Ago - Edited Well, "git clone" allows for a "depth" parameter that lets you specify how many commits you want to retain, and a "shallow-since" that lets you specify a time range.https://git-scm.com/docs/git-cloneYou would also want to exclude tags if you want a small repository (not sure if that's implicit when it's a single branch clone; the documentation makes it sound like it needs to be explicit).git clone --depth=1 --branch master --no-tags git@github.com:liferay/liferay-portal.gitI tested from home, and the clone takes about 6 minutes and the resulting repository uses 4 GB, with 2 GB inside of the .git folder.However, a shallow clone means that you have to use the GitHub UI in order to navigate history, because your local copy has no history at all. So, while the resulting file size is smaller and it does take less time to clone, the tedium of not being able to use local tooling makes it less desirable.But maybe that's just my biased opinion, since my day to day work requires navigating the repository history. Please sign in to reply. Reply as... Cancel Sushil Patidar Minhchau Dang 6 Years Ago Thanksit's a great help. After liferay source build is complete. if it is needed to build a particular module only let say shopping module. Is it feasible?Reragds Please sign in to reply. Reply as... Cancel Minhchau Dang Sushil Patidar 6 Years Ago Yes. If you've built the whole thing from source, you can deploy individual modules after that. The second blog in this series has an example where it redeploys the dynamic-data-mapping-data-provider-instance module.https://web.liferay.com/web/minhchau.dang/blog/-/blogs/troubleshooting-liferay-from-source#step-6-test-your-changes-part-1 Please sign in to reply. Reply as... Cancel
Sushil Patidar Minhchau Dang 6 Years Ago Thanksit's a great help. After liferay source build is complete. if it is needed to build a particular module only let say shopping module. Is it feasible?Reragds Please sign in to reply. Reply as... Cancel Minhchau Dang Sushil Patidar 6 Years Ago Yes. If you've built the whole thing from source, you can deploy individual modules after that. The second blog in this series has an example where it redeploys the dynamic-data-mapping-data-provider-instance module.https://web.liferay.com/web/minhchau.dang/blog/-/blogs/troubleshooting-liferay-from-source#step-6-test-your-changes-part-1 Please sign in to reply. Reply as... Cancel
Minhchau Dang Sushil Patidar 6 Years Ago Yes. If you've built the whole thing from source, you can deploy individual modules after that. The second blog in this series has an example where it redeploys the dynamic-data-mapping-data-provider-instance module.https://web.liferay.com/web/minhchau.dang/blog/-/blogs/troubleshooting-liferay-from-source#step-6-test-your-changes-part-1 Please sign in to reply. Reply as... Cancel
Pete Sampler 5 Years Ago What exactly are the prerequisites on the development machine? Please sign in to reply. Reply as... Cancel Minhchau Dang Pete Sampler 5 Years Ago If you want to build Liferay from source after cloning the Git repository, you will want 16+ GB RAM and 200+ GB of hard disk space. Please sign in to reply. Reply as... Cancel Pete Sampler Minhchau Dang 5 Years Ago S Please sign in to reply. Reply as... Cancel Pete Sampler Minhchau Dang 5 Years Ago Sorry for being too vague. I'd rather know which software/versions need to be installed to make a successful build. Please sign in to reply. Reply as... Cancel Minhchau Dang Pete Sampler 5 Years Ago The CONTRIBUTING guide is a little outdated in terms of hardware (it states that you can build Liferay with 8 GB of RAM, which is no longer true), but the software is listed in the System Requirements section is still true. https://github.com/liferay/liferay-portal/blob/master/CONTRIBUTING.markdown As for versions, it's odd that we didn't list it, but you need Ant 1.9.x (there are some cryptic errors when you use Ant 1.10.x) and the latest JDK 1.8 (I don't remember exactly when it was fixed, but there was a JDK bug that prevented Liferay from building). The build process will invoke the Gradle wrapper to download the version of Gradle it needs. For environment variables, you need your ANT_OPTS set to allow at least 4 GB of memory to be used (-Xmx4g -Xms4g). If you have a slower machine, you'll also want to set ANT_OPTS to limit the number of Gradle workers (-Dorg.gradle.workers.max=1). Please sign in to reply. Reply as... Cancel
Minhchau Dang Pete Sampler 5 Years Ago If you want to build Liferay from source after cloning the Git repository, you will want 16+ GB RAM and 200+ GB of hard disk space. Please sign in to reply. Reply as... Cancel Pete Sampler Minhchau Dang 5 Years Ago S Please sign in to reply. Reply as... Cancel Pete Sampler Minhchau Dang 5 Years Ago Sorry for being too vague. I'd rather know which software/versions need to be installed to make a successful build. Please sign in to reply. Reply as... Cancel Minhchau Dang Pete Sampler 5 Years Ago The CONTRIBUTING guide is a little outdated in terms of hardware (it states that you can build Liferay with 8 GB of RAM, which is no longer true), but the software is listed in the System Requirements section is still true. https://github.com/liferay/liferay-portal/blob/master/CONTRIBUTING.markdown As for versions, it's odd that we didn't list it, but you need Ant 1.9.x (there are some cryptic errors when you use Ant 1.10.x) and the latest JDK 1.8 (I don't remember exactly when it was fixed, but there was a JDK bug that prevented Liferay from building). The build process will invoke the Gradle wrapper to download the version of Gradle it needs. For environment variables, you need your ANT_OPTS set to allow at least 4 GB of memory to be used (-Xmx4g -Xms4g). If you have a slower machine, you'll also want to set ANT_OPTS to limit the number of Gradle workers (-Dorg.gradle.workers.max=1). Please sign in to reply. Reply as... Cancel
Pete Sampler Minhchau Dang 5 Years Ago Sorry for being too vague. I'd rather know which software/versions need to be installed to make a successful build. Please sign in to reply. Reply as... Cancel Minhchau Dang Pete Sampler 5 Years Ago The CONTRIBUTING guide is a little outdated in terms of hardware (it states that you can build Liferay with 8 GB of RAM, which is no longer true), but the software is listed in the System Requirements section is still true. https://github.com/liferay/liferay-portal/blob/master/CONTRIBUTING.markdown As for versions, it's odd that we didn't list it, but you need Ant 1.9.x (there are some cryptic errors when you use Ant 1.10.x) and the latest JDK 1.8 (I don't remember exactly when it was fixed, but there was a JDK bug that prevented Liferay from building). The build process will invoke the Gradle wrapper to download the version of Gradle it needs. For environment variables, you need your ANT_OPTS set to allow at least 4 GB of memory to be used (-Xmx4g -Xms4g). If you have a slower machine, you'll also want to set ANT_OPTS to limit the number of Gradle workers (-Dorg.gradle.workers.max=1). Please sign in to reply. Reply as... Cancel
Minhchau Dang Pete Sampler 5 Years Ago The CONTRIBUTING guide is a little outdated in terms of hardware (it states that you can build Liferay with 8 GB of RAM, which is no longer true), but the software is listed in the System Requirements section is still true. https://github.com/liferay/liferay-portal/blob/master/CONTRIBUTING.markdown As for versions, it's odd that we didn't list it, but you need Ant 1.9.x (there are some cryptic errors when you use Ant 1.10.x) and the latest JDK 1.8 (I don't remember exactly when it was fixed, but there was a JDK bug that prevented Liferay from building). The build process will invoke the Gradle wrapper to download the version of Gradle it needs. For environment variables, you need your ANT_OPTS set to allow at least 4 GB of memory to be used (-Xmx4g -Xms4g). If you have a slower machine, you'll also want to set ANT_OPTS to limit the number of Gradle workers (-Dorg.gradle.workers.max=1). Please sign in to reply. Reply as... Cancel
Paras Seith 5 Years Ago Any idea how to compile the Liferay NetBeans Source project. I have downloaded the source from liferays website. Tried opening it in netbeans project but no clue how to compile it. Link for the downloads: https://sourceforge.net/projects/lportal/files/Liferay%20Portal/7.1.1%20GA2/liferay-ce-portal-src-7.1.1-ga2-20181101125651026.zip/download Please sign in to reply. Reply as... Cancel