Adjusting Grails Application and Deployment If you omit the passowrd in the properties file, you will be anyway asked to provide it dierctly in the command prompt during the deployment process.
Grails maven install code#
Avoid putting your NetWeaver Cloudpassword in the properties file, as it may eventually end up in your code repository, which could make it visible to the other people. NetWeaver Cloud SDK path – the directory where you unpacked the SDK, your account name, desired application name and user name). You should adjust this properties to your local settings (e.g. To keep things simple, I pasted below the main properties that are necessary to deploy the application on NetWeaver Cloud: Plugin requires an external configuration file nwcloud.properties that should be put in the project root directory.Įxample of this configuration can be found on the plugin GitHub page. To use the plugin you need to add following lines in the build/plugins section of the project’s pom.xml: Configuring SAP NetWeaver Cloud Deployment Plugin Maven artifact id is taken by default from the Grails project name (so in our example it is hello-grails). The only parameter of this command is the group id (here I put com.sap) for the Maven bundle. Now we need to “mavenize” project and here comes the new Grails command create-pom: I will create application called hello-grails: We start by creating standard Grails application. Now you will be able to use the plugin in your Maven projects.
Grails maven install install#
Afterwards you just need to install it into your local Maven repository by simply running Maven install command in the project directory:Īnd that’s all. The easiest way to get it is to clone the Git repository from its GitHub page. To simplify NetWeaver Cloud deployment tasks in Maven, there is great nwcloud-maven-plugin. Installing SAP NetWeaver Cloud Deployment Plugin for Maven I was using version 3.0.4, but the example should run with most versions of Maven (I would assume all 2.x and 3.x versions should work fine, I haven’t spotted any restrictions from the SAP NetWeaver Cloud Deployment Plugin, but to be sure you should probably have at least version 3.x). You should also have a Maven installation on your machine.
It comes with useful updates that would be helpful in this scenario, like simplified way to convert non-mavenized Grails app by creating for us pom.xml with all necessary configuration and dependencies. I was using the latest Grails version to date (2.1.1).
Grails maven install how to#
With a few minor adjustments and the help of SAP NetWeaver Cloud Deployment Plugin for Maven, I will show how to automate the deployment process of Grails application. web applications written in Groovy and Grails.
As SAP NetWeaver Cloud is a platform for Java web applications, there is no problem with deploying web application initially running in another framework coming from the wider JVM-supported languages family, e.g.
0 kommentar(er)
