Jose Jimenez 5 Years Ago Thanks for sharing! Could you open a ticket in https://issues.liferay.com ? :) Please sign in to reply. Reply as... Cancel
Milen Dyankov 5 Years Ago - Edited Nice catch Andrew! Thank you for putting this in the from of valuable information for all Liferay developers. It's nice to see people doing that instead of rushing to call us names and publicly mock us (which, I personally think, we kind of deserve in this particularly embarrassing case). What you have discovered is a side effect of an attempt to deal with a nasty CI related issue: https://issues.liferay.com/browse/LPS-64541. I have notified the team about it and they will prioritize and fix it accordingly. I'll keep you posted. That said, and despite the fact your post explains it perfectly fine, it would be nice if you can open an issue so we can formally track it in Jira. Please sign in to reply. Reply as... Cancel Andrew Jardine Milen Dyankov 5 Years Ago voila: https://issues.liferay.com/browse/LPS-88409 Please sign in to reply. Reply as... Cancel
Andrew Jardine Milen Dyankov 5 Years Ago voila: https://issues.liferay.com/browse/LPS-88409 Please sign in to reply. Reply as... Cancel
Divyang J Patel 4 Years Ago Thanks Andrew for nice article, I am also facing the same issue "Exiting JVM" in my local machine. In my machine, JENKINS_HOME environment variable was set in my system settings variables. Which was causing to shutdown a liferay DXP tomcat. I have unset JENKINS_HOME variable, restarted liferay DXP and deployed plugin with import package error. Tomcat will remains on after throwing import package error by plugin. Please sign in to reply. Reply as... Cancel