Ask Questions and Find Answers

Hi Jamie,

I added Widfly 23.0 and I am still get the exception 

Caused by: org.jboss.modules.ModuleNotFoundException: com.liferay.portal when I startws the server (standalone.bat). 

Below is server.log I had o take out some portion f system config out of the log to not expose. But I do notice that ita set the modue path (module.path = C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\modules) and I am not sure if its lookingfor portal class. Please advise. Thanks :)

2022-02-01 13:48:45,003 INFO  [org.jboss.modules] (main) JBoss Modules version 1.11.0.Final
2022-02-01 13:48:45,481 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.12.Final
2022-02-01 13:48:45,493 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
2022-02-01 13:48:45,625 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Preview 23.0.0.Final (WildFly Core 15.0.0.Final) starting

2022-02-01 13:48:45,632 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\log\server.log -Dlogging.configuration=file:C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\configuration/logging.properties 
2022-02-01 13:48:46,476 INFO  [org.wildfly.security] (ServerService Thread Pool -- 9) ELY00001: WildFly Elytron version 1.15.1.Final
2022-02-01 13:48:46,968 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2022-02-01 13:48:46,991 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
2022-02-01 13:48:47,261 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found ROOT.war in deployment directory. To trigger deployment create a file called ROOT.war.dodeploy
2022-02-01 13:48:47,285 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2022-02-01 13:48:47,304 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.8.4.Final
2022-02-01 13:48:47,312 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.8.4.Final
2022-02-01 13:48:47,394 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 51) WFLYHEALTH0001: Activating Base Health Subsystem
2022-02-01 13:48:47,408 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 54) WFLYRS0016: RESTEasy version 3.15.1.Final
2022-02-01 13:48:47,409 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 52) WFLYCLINF0001: Activating Infinispan subsystem.
2022-02-01 13:48:47,424 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
2022-02-01 13:48:47,441 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
2022-02-01 13:48:47,461 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 62) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
2022-02-01 13:48:47,463 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 64) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
2022-02-01 13:48:47,463 INFO  [org.wildfly.extension.microprofile.jwt.smallrye._private] (ServerService Thread Pool -- 63) WFLYJWT0001: Activating WildFly MicroProfile JWT Subsystem
2022-02-01 13:48:47,463 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 59) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
2022-02-01 13:48:47,480 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 65) WFLYNAM0001: Activating Naming Subsystem
2022-02-01 13:48:47,482 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
2022-02-01 13:48:47,482 INFO  [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 1.4.27.Final)
2022-02-01 13:48:47,484 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
2022-02-01 13:48:47,518 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 61) WFLYMETRICS0001: Activating Base Metrics Subsystem
2022-02-01 13:48:47,545 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 2.2.5.Final starting
2022-02-01 13:48:47,586 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-1) WFLYELY00023: KeyStore file 'C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\configuration\application.keystore' does not exist. Used blank.
2022-02-01 13:48:47,627 INFO  [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service
2022-02-01 13:48:47,682 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2022-02-01 13:48:47,686 WARN  [org.wildfly.extension.elytron] (MSC service thread 1-1) WFLYELY01084: KeyStore C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self-signed certificate for host localhost
2022-02-01 13:48:48,781 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 53) WFLYIO001: Worker 'default' has auto-configured to 16 IO threads with 128 max task threads based on your 8 available processors
2022-02-01 13:48:48,786 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
2022-02-01 13:48:48,786 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
2022-02-01 13:48:48,846 INFO  [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Preview cumulative patch ID is: base, one-off patches include: none
2022-02-01 13:48:48,852 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.20.Final
2022-02-01 13:48:48,873 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
2022-02-01 13:48:48,876 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) Queuing requests.
2022-02-01 13:48:48,877 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
2022-02-01 13:48:48,892 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
2022-02-01 13:48:48,896 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\liferay\7.4\liferay-ce-portal-7.4.3.8-ga8\wildfly-23.0.0\standalone\deployments
2022-02-01 13:48:48,910 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "ROOT.war" (runtime-name: "ROOT.war")
2022-02-01 13:48:48,962 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
2022-02-01 13:48:49,023 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
2022-02-01 13:48:49,300 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
2022-02-01 13:48:49,301 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2022-02-01 13:48:49,418 INFO  [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.4.2.Final (Apache CXF 3.3.9) 
2022-02-01 13:48:50,258 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.module.service."deployment.ROOT.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.ROOT.war".main: WFLYSRV0179: Failed to load module: deployment.ROOT.war
    at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:116)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
    at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
    at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.modules.ModuleNotFoundException: com.liferay.portal
    at org.jboss.modules.Module.addPaths(Module.java:1288)
    at org.jboss.modules.Module.link(Module.java:1644)
    at org.jboss.modules.Module.relinkIfNecessary(Module.java:1672)
    at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:303)
    at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:287)
    at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:93)
    ... 8 more

2022-02-01 13:48:50,264 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.ROOT.war\".main" => "WFLYSRV0179: Failed to load module: deployment.ROOT.war
    Caused by: org.jboss.modules.ModuleNotFoundException: com.liferay.portal"}}
2022-02-01 13:48:50,339 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 44) WFLYSRV0010: Deployed "ROOT.war" (runtime-name : "ROOT.war")
2022-02-01 13:48:50,341 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.module.service."deployment.ROOT.war".main: WFLYSRV0179: Failed to load module: deployment.ROOT.war

2022-02-01 13:48:50,408 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2022-02-01 13:48:50,411 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Preview 23.0.0.Final (WildFly Core 15.0.0.Final) started (with errors) in 5969ms - Started 320 of 567 services (2 services failed or missing dependencies, 352 services are lazy, passive or on-demand)
2022-02-01 13:48:50,415 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2022-02-01 13:48:50,415 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
 

It's because jboss-deployment-structure.xml in ROOT.war/WEB-INF is still looking for modules that are now bundled with the war file.

I modified my $WILDFLY_HOME/standalone/deployments/ROOT.war/WEB-INF/jboss-deployment-structure.xml to look like the following and it works for me now:

<?xml version="1.0"?>

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
	<deployment>
		<exclusions>
			<module name="org.apache.log4j" />
			<module name="org.hibernate" />
			<module name="org.slf4j" />
		</exclusions>
		<dependencies>
			<module name="org.apache.xerces" />
			<module name="org.jboss.modules" />
		</dependencies>
	</deployment>
</jboss-deployment-structure>

Hi Jamie, ROOT.war got deployed when I removed the refernce <module meta-inf="export" name="com.liferay.portal">
                <imports>
                    <include path="META-INF" />
                </imports>
            </module>
            <module name="javax.mail.api" />

in the jboss-deployment-stucture.xml but it doesnt start the liferay server nor load the liferay modules. How do we get it start the lferay server and modules. I am now using liferay-ce-portal-7.4.3.9-ga9. 

Thanks

Kevin

Hi Kevin, taking a guess, it may be possible that the contents from the osgi zip file are in the wrong location.  It should be located in a directory above the wildfly home directory and have the name osgi/marketplace where the marketplace directoy has a bunch of .lpkg files in it.

For example here is how I have mine:

I have it in the directory above widlfy. It only has a market folder.

But looking through the server.log file i see WARNING as shown below. Could this be the issue it desnt start liferay 

2022-02-02 10:34:04,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "ROOT.war" (runtime-name: "ROOT.war")
2022-02-02 10:34:05,454 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.ui.SearchIteratorTag due to an exception (enable DEBUG log level to see the cause)
2022-02-02 10:34:05,454 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.ui.BreadcrumbTag due to an exception (enable DEBUG log level to see the cause)
2022-02-02 10:34:05,454 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.aui.NavBarTag due to an exception (enable DEBUG log level to see the cause)
2022-02-02 10:34:05,454 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.portletext.PreviewTag due to an exception (enable DEBUG log level to see the cause)
2022-02-02 10:34:05,455 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.ui.SearchContainerColumnTextTag due to an exception (enable DEBUG log level to see the cause)
2022-02-02 10:34:05,455 WARN  [org.jboss.as.ee] (MSC service thread 1-7) WFLYEE0007: Not installing optional component com.liferay.taglib.util.HtmlBottomTag due to an exception (enable DEBUG log level to see the cause)

Hi Jamie, I ran with wildfly 18 and still get the warinings but now I am getting out of memory issues what start up  liferay. See below

Please provide the jar on your classpath to parse sqlite files.
See tika-parsers/pom.xml for the correct version.
2022-02-04 11:59:04,528 INFO  [stdout] (Start Level: Equinox Container: 0931c7fc-c04a-4ef0-ae3e-e0ad918f2045) 2022-02-04 11:59:04,524 Start Level: Equinox Container: 0931c7fc-c04a-4ef0-ae3e-e0ad918f2045 ERROR An exception occurred processing Appender TEXT_FILE org.apache.logging.log4j.core.appender.AppenderLoggingException: java.lang.OutOfMemoryError: GC overhead limit exceeded

Here is my setting in standalone.conf file

JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=UTF-8 -Djava.locale.providers=JRE,COMPAT,CLDR -Djava.net.preferIPv4Stack=true -Dlog4j2.formatMsgNoLookups=true -Duser.timezone=GMT -Xms2560m -Xmx2560m -XX:MaxNewSize=1536m -XX:MaxMetaspaceSize=768m -XX:MetaspaceSize=768m -XX:NewSize=1536m -XX:SurvivorRatio=7"

Hi Kevin,

I ended up having to adjust my memory settings to get it to run because I think the initial deployment requires a lot of memory to run.  Here is what I used:

set "JAVA_OPTS=-Dfile.encoding=UTF-8 -Djava.locale.providers=JRE,COMPAT,CLDR -Djava.net.preferIPv4Stack=true -Dlog4j2.formatMsgNoLookups=true -Duser.timezone=GMT -Xms2560m -Xmx4096m -XX:MaxNewSize=1536m -XX:MaxMetaspaceSize=1536m -XX:MetaspaceSize=768m -XX:NewSize=1536m -XX:SurvivorRatio=7"

Hi Jamie, it seems my local PC maybe runningout of memmory so when i start liferay running under wildfly 18 on my development server but getting the floowing errors and liferayis not starting. Please see below. 

 Unable to sync callable
com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionNotInitializedException: Elasticsearch connection not found. Production Mode Enabled: false, Connection ID: null, Prefer Local Cluster: false, Cross-Cluster Replication Enabled: false. Enable INFO logs on class com.liferay.portal.search.elasticsearch7.internal.connection.ElasticsearchConnectionManager for more information

Declarative Service {id: 7640, name: com.liferay.mobile.device.rules.web.internal.portlet.action.EditRuleMVCActionCommand, unsatisfied references: _            {name: MDRRuleService, target: null}_   }_Bundle {id: 921, name: com.liferay.portal.mobile.device.recognition.impl, version: 4.0.6}_    Declarative Service {id: 3739, name: com.liferay.portal.mobile.device.recognition.internal.rule.group.DefaultRuleGroupProcessorImpl, unsatisfied references: _          {name: MdrRuleGroupInstanceLocalService, target: null}_         {name: MdrRuleGroupLocalService, target: null}_ } [Sanitized]
2022-02-04 20:38:33.272 INFO  [ServerService Thread Pool -- 77][SystemCheckOSGiCommands:114] Running "Spring Extender Unavailable Component Checker". You can run this by itself with command "dm na" in gogo shell.
2022-02-04 20:38:33.276 WARN  [ServerService Thread Pool -- 77][SystemCheckOSGiCommands:137] Spring Extender Unavailable Component Checker check result: _Bundle {id: 794, name: com.liferay.mobile.device.rules.service, version: 5.0.13}._    Component with ID 134 is unavailable due to missing required dependencies:_             service dependency [com.liferay.portal.kernel.model.Release (&(release.bundle.symbolic.name=com.liferay.mobile.device.rules.service)(&(release.schema.version>=2.1.0)(!(release.schema.version>=3.0.0)))(|(!(release.state=*))(release.state=0)))] [Sanitized]

Maybe it has to do with the deployment not completing properly due to the out of memory error.  Can you try deleting the directories elasticsearch-sidecar and osgi/state and try it again?

Hi Kevin, glad to hear you got it working! 

Upgrades are a much larger topic.  As for upgrades I know you said you can't use the upgrade planner but I would strongly encourage using it.  Even if you don't normally use Liferay Developer Studio for day to day development it could be used for the upgrade process alone and then you can go back to using your normal IDE.  It will greatly simplify the upgrade process guiding you through the most common upgrade steps and will actually make a lot of the required changes automatically.

Also if you run into specific issues you should ask new questions related to those issues in the development category as this question dealt with running on Wildfly and not upgrade issues.

Hi Jamie, yes I agree that upgrade issue will be another topic. But I do use the Liferay Developer studio. The upgrade planner is only use if you are migraitng from 6+,7.1 to 7.2. Since I currently have 7.2 the upgrade planner doesnt support moving from 7.2 to 7.4 . https://help.liferay.com/hc/en-us/articles/360029147451-Liferay-Upgrade-Planner

Hi Kevin, sorry I misunderstood.  I thought you weren't being allowed to use Liferay Developer Studio for some reason.  I looked earlier today and I had a 7.4 option using version 3.9.5-ga6 .  You may need to upgrade to the latest version found here: https://liferay.dev/-/ide-installation-instructions

Hi Kevin, when I tried it on Windows I got 3.9

​​​​​​​

Hi Kevin, I have been looking into this more and have learned some new things. Wildfly 23.0 does not seem to work with Developer Studio at all but Wildfly 18.0 does. I have asked our developer tooling team about supporting 23.0 but haven't heard back yet. I have learned that I can produce a Wildfly bundle from the liferay source and have learned there is a couple of differences from what I told you that may have an impact on this:

• Make sure to use the Java EE Full & Web Distribution download as it contains some javax classes that Liferay uses.
• Instead of modifying jboss-deployment-structure.xml create a new liferay modules config file with dependence being declared in the config file.

Here is the Wildfly 18.0 config that the build process produced: wildfly-18.0.0-liferay-config.zip

I will also look into updating the docs to make sure to cover the missing config which right now it appears to be Windows JVM tuning and the missing JBoss module config.

Thanks Jamie for the feedback. Do you know when the docs will be ready to cover the missing configuration for Windows JVM tuning and the missing JBoss module config.? Also, will the documentation be updated under this link https://learn.liferay.com/dxp/latest/en/installation-and-upgrades/installing-liferay/installing-liferay-on-an-application-server/installing-on-wildfly.html? Will documentation cover Widfly18 and 23.0?

Thanks

kevin 

Hi Kevin, I wanted to update you on Wildfly 23 support in Liferay Developer Studio.  We have added support for it here: https://issues.liferay.com/browse/IDE-5064 and will be in the next version of Developer Studio.  We also have a snapshot version that you can try yourself but it seemed to work okay for me on Windows: https://drive.google.com/drive/folders/1oFjvtFlHMvSp-BtUlhMtuCehpyxBvjuI?usp=sharing

Hi Kevin, I haven't tried building themes in 7.4.  I'm not aware of the process being any different though.  When I migrated liferay.dev to 7.4 I moved to a themeless setup using Master Pages.

Thanks Jamie for your response. I found the solution you will need to a liferay generator 10 to get access to liferay 7.4. However, I decided not to use the theme generator this time but used the Liferay Studio IDE to create a theme in which I was able to create theme thtas comes with a giradle build file.