Message Boards

what is different between dxp and portal of product version of workspace

Scarletake Bwi, modified 2 Years ago.

what is different between dxp and portal of product version of workspace

Expert Posts: 326 Join Date: 12/20/10 Recent Posts

hi

now i try liferay 7.4 ga1, and i have to upgrade my workspace from 7.3.5 to 7.4

i only know from document liferay-portal-7-4-ce-ga1-release

i modified gradle.property and refrash gradle

liferay.workspace.product = portal-7.4-ga1

but it not work well, service builder not work well.

i'd like to know, what i miss, and i am also try crate a new workspace

what is different between dxp and portal of product version of workspace? i always use the default workspace boundle in LiferayWorkspacewithDevStudio, and my liferay is community version.

thank you

 

thumbnail
Christoph Rabel, modified 2 Years ago.

RE: what is different between dxp and portal of product version of workspac

Liferay Legend Posts: 1554 Join Date: 9/24/09 Recent Posts

See GETTING_STARTED.markdown (in the workspace, maybe create a new one to get the most current version of that file) for an explanation of the setting.

The (arguably) most important thing it does is to define which dependencies to use. So, instead of specifying in the build.gradle which portal kernel you want to target with your module, you can skip that and just write:

compileOnly group: "com.liferay.portal" , name: "com.liferay.portal.kernel"

The version is determined automatically which is really nice when you upgrade.

BUT, as mentioned in the other thread, this does not control everything. Another important setting can be found in the "settings.gradle" file, namely the version of "com.liferay.gradle.plugins.workspace".

The workspace defines which plugins to use before/during/after the build. So, when you change the gradle plugins workspace version, you could get a newer version of e.g. the service builder plugin, that creates the service builder files. (You can find a list of plugins here: https://github.com/liferay/liferay-portal/tree/master/modules/sdk )

So, when you update that setting and call "buildService" it will (probably) also use a newer service builder plugin version and give you different files. Sometimes the changes are minor, sometimes they are breaking ...