liferay-maven-plugin + direct-deploy configuration for DXPliferay-maven-plugin + direct-deploy configuration for DXPhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1193098032024-03-28T08:57:50Z2024-03-28T08:57:50ZRE: liferay-maven-plugin + direct-deploy configuration for DXPDominik Markshttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193135182020-06-04T09:55:40Z2020-06-04T09:55:40ZAs far as I know the maven plugin has been removed and will not work for Liferay 7.x. So you have to copy the WAR file to the deploy folder. Dominik Marks2020-06-04T09:55:40ZRE: liferay-maven-plugin + direct-deploy configuration for DXPS Nhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193110962020-06-04T07:51:27Z2020-06-04T07:51:27ZAnyone? Please? I'm leaning toward just getting rid of the plugin section from POM and deploying the hook in Liferay's deploy folder (rather than the server's webapps folder which would necessitate said preprocessing), since it doesn't look like preprocessing is supported in 7.x. Would be great to get confirmation of this though.S N2020-06-04T07:51:27Zliferay-maven-plugin + direct-deploy configuration for DXPS Nhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1193098022020-06-03T18:51:08Z2020-06-03T18:51:08Z<html><head></head><body>I'm new to Liferay 7.x, but have some 6.2 experience. My project is currently on Liferay 6.2 (with Tomcat), and I have configured the liferay-maven-plugin in my Liferay hook project's maven pom.xml as below, in order to pre-process my hook WAR for hot deployment (using the direct-deploy goal of the plugin). I can copy the generated WAR and put it in tomcat/webapps folder directly, and it will get picked up by Liferay - our deployment scripts do the same.<br><br><pre><code><plugin>
<groupid>com.liferay.maven.plugins</groupid>
<artifactid>liferay-maven-plugin</artifactid>
<version>6.2.1</version>
<executions>
<execution>
<id>pre-process-war</id>
<phase>package</phase>
<goals>
<goal>direct-deploy</goal>
</goals>
</execution>
</executions>
<configuration>
<appserverdeploydir>${project.basedir}/target/liferay-pre-process</appserverdeploydir>
<liferayversion>6.2.1</liferayversion>
<plugintype>hook</plugintype>
<unpackwar>false</unpackwar>
</configuration>
</plugin></code></pre><br><br>I'm now trying to migrate this hook to Liferay 7.2.1 CE. There is no plan to redesign this as an OSGI module at the moment i.e. it would continue to be packaged as a WAR. So how would my new direct-deploy configuration look like, with Liferay 7.2.1, so that I can achieve the same? Specifically:<br><br>a) Can I continue using the same Maven plugin? I see from the docs that the liferay-maven-plugin has been "removed", yet my understanding from other help pages is that this plugin should not be used only with the newer, OSGI-module style plugins (the latter makes more sense to me).<br><br>b) If I can continue using the same Maven plugin, which version of the plugin works with 7.2.1? Also, which liferayVersion value should I use here? I tried a bunch of combinations and none of them worked.<br><br>For instance, I first tried liferayVersion 7.2.1 but the build failed while running the direct-deploy goal, since Maven didn't find a com.liferay.portal:portal-web artifact with that version. So I tried the latest version of that artifact from Maven Central, which is 7.0.2, as my liferayVersion. But the build failed again, this time because it couldn't locate the corresponding version of com.liferay.portal:portal-service. There's no 7.x version of portal-service though, wh