Environment set-up for Liferay server and integrate wif Tableau/Informatica Reporting application server.Sr Liferay Developer and Liferay Architect Source Code Management: GIT, SVN, Team Foundation Version Control, VSS, CVS, Perforceĭevelopment: Eclipse, Maven, Ant, JRebel, Jenkin, Hudson and Bamboo (Atlassian)ĭefect Tracking: HP-ALM/QC, Rational Clear Quest Java and UI: Java, JSP, Servlets, JQuery, JSON, DHTMLX, Data tables, Log4j, Sl4jĪpplication Server: Glassfish, Websphere, JBoss, TomcatĪutantication: LDAP wif CAS, Liferay, Siteminder, OAuth, SSO as IDP/SP using SAML2.0Ĭontent Repositories: Liferay Enterprise, AlfrescoĪnalytics: Google Analytics, Google Tag Manager, New Relic Liferay: JSR168, JSR 286, JSR 362, Liferay Administrator, Web Content Management, Hooks, Theme, Clustering, Autantication, Workflow, Structures, Page Templates, Inter - Portlet Communication(IPC), Service Builder, 3rd party integration, Liferay Roles/Organization/Sites, Cross domain communication, Environment set-up I has participated and lead on teams doing analysis, design, development, implementations, enhancements and testing of applications in these main core technologies: Liferay, Java and Ariba technologies.Over 16+ yrs of IT experience in Portal, Web based and Java technologies. It is quite common that developers write bash/batch scripts which clean the targets, build the necessary stuff, pick up the wars and copy them to the deploy folder. Or you can you can write a deployment script which will do the necessary manual tasks for you. For example if you want to use the "dev" profile: For example: dev your-module ejbs-for-your-module Īfter that you can build your project using the profile with Maven. You can add a new profile there with the modules specified. In your main (top-level) pom.xml there's a tag called profiles. Tip: If you want to simplify your doployment using the auto-deploy method (folder "deploy") then you can speed it up by specifying only the modules that you want to build, by creating a profile: Hope it helps you a bit if you don't want to use JRebel. This doesn't work if you change the structures of your classes too much, or change the arguments of the method, but it is a great help when your trying to fix for example a null pointer inside your methods body. Afterwards disconnect/end the debugging and go check your changes! When you do some changes in your code and you want to test it just connect to your running application server as if you were going to debug it remotely and compile the class you changed. If you don't want to redeploy the whole module which needs to be built you can hot-deploy it with IDEA if you have your server configured to allow remote debugging. Now for the answer-ish part: This may be more of a tip, than an exact solution, but I have been using this for a long time. Don't discard this option - you might want to check out this tutorial or maybe this one. However, even though I don't use JRebel personally I've heard a lot of positive reactions from colleagues who are using it. How to program portlets efficiently using Liferay and Maven? -> I want to configure Intellij IDEA, don't want to use another IDE. Technically this is autodeployment, because it's handled by your application server's AutoDeploy Scanner, but it's probably not what you mean by automatic deployment or hot-deploy. war file into liferay deploy directory and that's not autodeploy. war file on a server (Liferay+Tomcat Bundle) -> Talks about droping. Maven project using archetype: liferay-portlet-archetype.ĭeploy.war file in IDEA to deploy to Liferay -> Checked. How to program portlets efficiently using Liferay and Maven? -> I want to configure Intellij IDEA, don't want to use another IDE.war file into liferay deploy directory and that's not hot-deploy. I also tried with the following questions but no result: I tried with Running Liferay from IntelliJ (from Liferay Wiki) but can't get it to work. That's why I want to build, start Tomcat (bundled with LifeRay) and deploy my portlet with everything through Intellij IDEA, with hot-deployment enabled. war to LifeRay's auto-deploy directory to finally wait (again) till LifeRay finishes deploying it. I'm developing a Liferay portlet and I can't stand waiting for Maven to build the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |