Liferay 6.2 CE GA4 Now Available

I'm very happy to announce the release of Liferay Portal 6.2 CE GA4! Download it now: [Tomcat Bundle] [JBoss Bundle] [GlassFish Bundle] [Source Code] [Other bundles and Files] [Quick Start] [Detailed Install Instructions].

Once again, this release is particularly noteworthy. Why is that? Well, if you attended DevCon in Germany last year, you probably don't remember it, but I promised you a regular 6-month community maintenance release cadence, starting with the 6.2 CE GA3 release on January 15th. And on January 15th, we did it: we released GA3.

And then guess what? You discovered a fatal flaw in GA3 that was particularly annoying and impactful, especially on the "first impression" of Liferay. After some discussion in the community we all agreed a new release was needed rather than wait the usual 6 months, so here we are 3 months later with a new release that includes your most requested fixes, along with many others. It's great to see such cooperation! You spoke, we listened (and you spoke and we listened again), you helped us fix it up, and now we release a GA4 that we hope will meet your needs better than ever!

Release Naming

Following Liferay's official versioning scheme, this release is Liferay Portal 6.2 CE GA4. The internal version number is 6.2.3. Future CE releases of 6.2 will be designated GA5, GA6, .. and so on. See below for upgrade instructions from 6.2.x, 6.1.x, 6.0.x, and 5.x.


You can find the 6.2 CE GA4 release on the usual downloads page. If you need additional files (for example, upgrade SQL scripts or dependency libraries), you can find them at the bottom of the downloads page.

Maven Artifacts

Developers can find this release in our Maven repository, and it should be showing up on Maven Central in the near future. As a reminder, you can also find Maven artifacts for Liferay 7 Milestone Releases (here's one of them) in the liferay-previews repository!

Source Code

As Liferay is an open source project, many of you will want to get at its guts. The source is available as a zip archive on the downloads page, or in its source code repository on Github. The repository has also been tagged for the release (as a reminder, the liferay-plugins repo no longer gets tags for portal releases as the plugins are de-coupled from core). Many community contributions went into this release, and hopefully many more in future releases! If you're interested in contributing, take a look at our new participate page on the Liferay Developer Network.

What's New / Changed?

This update fixes many issues [full list here], but here are some of the more important and/or popular ones that you may be interested in:

Known Issues

These are issues that were found during testing, but deemed not a showstopper (usually things are left as-is because they aren't severe (data loss/security breach), don't affect very many people, and there is a convenient workaround - luckily our 6 month cadence means you don't have to wait more than 6 months!). For details on workarounds, see the bug reports.

  • Writing to search index fails when Index Writer queue is full (LPS-54672
  • lucene/dump does not work when starting a node (LPS-54876)


The Liferay Documentation Team has been continuously adding and improving on the official documentation. This includes updated javadoc and related reference documentation, updated tutorials and learning paths, and a new home on the Liferay Developer Network. While still in beta, this site will also become the new home of our developer and technical communities.

Our community has been instrumental in identifying the areas of improvement, and we are constantly updating the documentation to fill in any gaps. Check out Rich's blog for more detail on how you can get involved.

Support Matrix

Liferay has published the official compatibility matrix for 6.1 and 6.2. This is the official support matrix for our Enterprise Subscription customers, but it's a pretty good reference for CE as well. If you're wondering where Java 8 support is at, it's expected in the next release and has already been added as supported platform for EE.

Liferay Marketplace

Most Liferay-authored Marketplace plugins were updated to support 6.2 GA1 when it was first released, and remain compatible with this updated GA4 release.

If you are a Marketplace Developer, and have authored a 6.2 CE GA1, GA2, or GA3-compatible app, you should ensure your app continues to work with this 6.2 CE GA4 release. It is Liferay's aim to remain compatible within a given release family, so in the unlikely event that your app works with GA3 but NOT GA4, you will need to make any necessary changes and re-submit, and let the Marketplace team know about any incompatibilities you discovered. Chances are you will have nothing to do (since you declared compatibility with 6.2.0+, which includes 6.2.3).

Bug Reporting

As always, the project continues to use to report and manage bug and feature requests. If you believe you have encountered a bug in the new release (shocking, I know), please be cognizant of the bug reporting standards and report your issue on, selecting the 6.2.3 CE GA4 release as the value for the Affects Version/s field.


Good news for those of you on 6.0 or prior! Liferay introduced the seamless upgrade feature with Liferay 6.1. Seamless upgrades allow Liferay to be upgraded more easily. In most cases, pointing the latest version of Liferay to the database of the older version is enough. There are some caveats though, so be sure to check out the Upgrading Liferay information on the Liferay Developer Network for more detail on upgrading to this release.

Getting Support

Support for Liferay 6.2 CE comes from the wonderful and active community, from which Liferay itself was nurtured into the enterprise offering it is today. Please visit the community pages to find out more about the myriad avenues through which you can get your questions answered, and check out the new Liferay Developer Network for technical resources during your Liferay journey.

Liferay and its worldwide partner network also provides services, support, training, and consulting around Liferay via its Enterprise Subscription.

Also note that customers on existing releases such as 6.0 and 6.1 continue to be professionally supported, and the documentation, source, and other ancillary data about these releases will remain in place.

What's Next

Of course we in the Liferay Community are interested in your take on the new features in Liferay 6.2 and the updates in this GA4 release. Work has already begun on the next evolution of Liferay, based on user feedback and community ideas. If you are interested in learning more, join our expedition team and see what's under the hood of Liferay 7!

As I mentioned earlier, we will start doing regular open source releases of Liferay Portal every 6 months, until the next major release. So if you find bugs in this or previous releases, and want to up their priority to get them fixed, be sure to use JIRA and vote for your favorite issues!


This release was produced by Liferay's worldwide portal engineering team, and involved many hours of development, testing, writing documentation, translating, testing some more, and working with the wider Liferay community of customers, partners, and open source developers to incorporate all sorts of contributions, both big and small. We are glad you have chosen to use Liferay, and hope that it meets or exceeds your expectations!

In addition to Liferay's engineering staff, a special thanks goes to the many open source developers who volunteered their time and energy to help with the release, whether it was bugfixing, idea generation, documentation, translations, testing, or other contribution that helped to improve this release. Check out the Community Contributor Hall of Fame and be sure to thank them if you run across them in the community (or add your name if you have contributed and are not listed).

The snapshots in the maven repo for L7 only go up to M2 even though M4 is available.
So, starting with M3 we decided to stop using snapshots for the milestone releases - it's a little confusing because the milestone releases are like "releases" (from the maven perspective) but we don't want to pollute the main CE repo with "releases" that aren't really releases. So they are now in the liferay-previews repo. e.g. here: you can see the M3 and M4 artifacts.
What about 6.2.3 maven artifact ? I can't found them in release repository
Marco - sorry for the delay - they should be available later today! We had an issue with our maven process that we're ironing out today.
Maven artifacts now posted to - eventually they will find their way to Maven Central! But the time delay is unpredictable.
It is still not quite ok I'm afraid : Failure to find com.liferay.maven.plugins:liferay-maven-plugin:jar:6.2.3 in
I was talking about portal-impl, portal-service, etc artifacts and I can confirm that those are available in the repository.
I think liferay-maven-plugin has a different release cycle....this is the main reason of having two different properties in the liferay archetype :
${liferay.version} and ${liferay.maven.plugin.version}
@Philippe - we'll be releasing the 6.2.3 Maven plugin to keep it in sync and reduce confusion - but there have been no changes in it since 6.2.2 so it should be OK to use the 6.2.2 version for ${liferay.maven.plugin.version}
Tag on github is not available. i.e. is broken. Kindly fix.
thanks a lot for the good work. However, I have some comments to make.

Firstly, the link to the source code bundle is broken, it retrieves the javadoc bundle, not the source code (at least with my version of Chrome). I can find the correct file from Sourceforge, though.

The second point is about not tagging the plug-ins in GitHub. There are a number of plugins delivered in the bundles (Calendar Portlet, Knowledge Base etc.). If I need to tweak any of them, how do I know which source code to fetch from GitHub to work on? Someone has to know from which versions of the plugins the bundle has been made of, so why not tag them?

Best Regards,
And I meant the source code download link on the actual download page The link on this page seems to be OK, though. Sorry for the confusion.
Hey Pasi - the source download link on the downloads page has been fixed - thanks!

As for tagging the liferay-plugins repo - unfortunately github tags apply to the entire repo, but not all plugins in that repo are tested or delivered with each CE release. So while we could tag it on the day of release, it wouldn't correspond to the binary you see on the Marketplace.

Each plugin has a liferay-releng.changelog file associated with it. If you look in that file you can see the github commits which produced the binary you see on Marketplace. So if you want to tweak, say, the youtube portlet - check out its changelog on Marketplace - - see that you're on the latest version as shown in its liferay-releng.changelog file here: and then see the git commit that produced it: it's commit 1077f05e0e0268b189e7c5d00d63d5376caa707d which can be seen here: - so if you want to tweak this, simply 'git checkout 1077f05e0e0268b189e7c5d00d63d5376caa707d' and you'll have the source.
I've seen Gradle included in the new Liferay 6.2 GA4 SDK. What is it for? It was not included in GA3.
Hey @Federico, Gradle is a different (and in my opinion better) build infrastructure tool, sort of like ant and maven but better than both.

You don't have to use it, but the Plugins SDK now wraps around and uses it. But you can still use ant or maven, we're just giving you more choice emoticon
So, it's just support to use it in our own plugins. Great to know it!

I've already checked it and seen that it's a lot let verbose and as powerful as maven.
@Federico , @James
Be aware that if you use gradle in Plugins SDK 6.2.3 you need to change many gradle files because at this moment liferay dependencies are hardcoded with the value of "7.0.0-SNAPSHOT"

This is my PR: on the master. You can check there the list of file changed to overcome the issue.
That's great that the SDK now has Gradle support. However, since the SDK seems to be going the way of the dodo (true?) , will there be a stand alone Gradle plugin similar to the Maven plugin ?
@Joseph -

The SDK will continue to live but it will begin migrating to gradle in the future to accomplish any packaging/building. We are also working on a different set of gradle plugins that are based on gradle conventions similar to Maven.

We understand the SDK is not for everyone but we also know many people have already incorporated the SDK into their workflow so we will be providing options for both types of developers.
OK. I'm good with either, just needed the clarification. How much gradle support is is in the current ga4 SDK release?
Everything in there is just in alpha state and has not been tested much for 6.2. Things may or may not work so... Our goal is to finish it for 7.0 and then backport it properly to 6.2