We control what modules (AMPs and JARs) that should be applied to each WAR and what webapps we want to run via Alfresco Maven plugin configuration: And the artifactId for the alfresco.war artifact has changed to alfresco-platform from version 5.2. Note that the Platform (alfresco.war) and Share (share.war) artifacts are now released with their own individual version numbers. This is still all done in the project POM properties section: There are a couple of things we need to feed the plugin with, such as what version of the different WAR artifacts we want to use, database configuration, location of alf_data etc. The plug-in now builds the project web applications as follows: This will make upgrades easier and you can now use your own Maven parent POM. This means that the POMs will be a lot slimmer and they will also not depend on a parent SDK POM. ![]() The most significant change is that we now keep most of the build logic, run logic, and project configuration inside the Alfresco Maven Plugin. Upgrading previous SDK 2.2 projects to SDK 3 IntroductionĪlfresco SDK 3 is a major overhaul of the SDK and provides several improvements on previous SDKs. Using a custom context path for the Share webappĪdding Custom System Properties when running Overriding Web Resources and Adding 3rd party Libraries (Using AMPs) 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.Support for different versioning of Platform and Share UI 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: Ī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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |