Module Version Changes Since DXP Release

When developing for Liferay, you usually prefer specifying the lowest possible version of the bundle or module that provides the API that you are consuming, as that maximizes the number of versions where your customization can successfully run. However, sometimes a community member or a customer knows that they aren't going to downgrade their Liferay, and they want to know, "What version of this bundle/module am I using in this version of DXP?" This page was created to answer that question.

Warning: This is NOT an official Liferay tool, nor is it supported by Liferay in any way. This does a source code analysis of the code that exists at the tag for the specified release. For Marketplace plugins (which are not recreated from source but rather released on a separate schedule), these versions will not be accurate.

Choose Your Comparison

Note: If the values in the select boxes are the same, this will list the versions of all modules at the specified baseline rather than a comparison. Artifacts from the com.liferay.portal group are listed as snapshots, because they really are snapshots (so the official artifact has not been released). If the version is listed as .1, use .0 at build time. If the version is listed as .0, you might be able to use .0 at build time if your package doesn't change before the actual .0 release, but you may have to use one minor version before the listed version at build time.
Starting VersionCheck Against VersionName FilterChanges Only

Comparison Results

Note: Entries with a gray background indicate a version change. Version 0.0.0 means that the module does not exist in that version of DXP.