Skip to main content

Gradle





build.gradle


Gradle builds a script file for handling two things; one is projects and another one is tasks.

task hello {
   doLast {
      println 'tutorialspoint'
   }
}     C:\> gradle –q hello

The Gradle script mainly uses two real Objects; 

  • Project Object 
  • Script Object.

Project Object − Each script describes about one or multiple projects. While in the execution, this script configures the Project Object. You can call some methods and use property in your build script which are delegated to the Project Object.
Script Object − Gradle takes script code into classes, which implements Script Interface and then executes. This means that of all the properties and methods declared by the script interface are available in your script.


Sr. No.NameTypeDefault Value
1projectProjectThe Project instance
2nameStringThe name of the project directory.
3pathStringThe absolute path of the project.
4descriptionStringA description for the project.
5projectDirFileThe directory containing the build script.
6buildDirFileprojectDir/build
7groupObjectUnspecified
8versionObjectUnspecified
9antAntBuilderAn AntBuilder instance


If you think task works similar to ANT’s target, then that’s right - Gradle task is equivalent to ANT target.

task hello << {
   println 'tutorialspoint'
}

task upper << {
   String expString = 'TUTORIALS point'
   println "Original: " + expString
   println "Upper case: " + expString.toUpperCase()}
C:\> gradle –q upper

Gradle build script describes one or more Projects. 


Each project is made up of different tasks. 

A task is a piece of work which a build performs.

 The task might be compiling 
  • some classes,
  • storing class files into separate target folder, 
  • creating JAR, 
  • generating Javadoc, 
  • or publishing some archives to repositories.


















Comments

Popular posts from this blog

Microservices Design patterns

What are microservices? Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of services that are Highly maintainable and testable Loosely coupled Independently deployable Organized around business capabilities Owned by a small team The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack. You are developing a server-side enterprise application. It must support a variety of different clients including desktop browsers, mobile browsers and native mobile applications. The application might also expose an API for 3rd parties to consume. It might also integrate with other applications via either web services or a message broker. The application handles requests (HTTP requests and messages) by executing business logic; accessing a database; exchanging messages with other systems; and returni...

GraphQL

What is GraphQL  API Standard invented & open-sourced by Facebook Alternative to  REST API  enables declarative data fetching  exposes single endpoint & responds to queries How it works?  Why Graphql? Improvises performance by reducing the data that is to be transferred over the internet Variety of different frontend frameworks and platforms on client-side Fast development speed & expectation for rapid feature development Why Graphql is better than REST? Flexibility & efficient  No more over /under fetching of data Over fetching : Under fetching: Insightful analytics  Schema serves as contract between client and server CORE CONCEPTS : SDL :SCHEMA DEFINITION LANGUAGE Writing Data with mutations 3 kinds of mutations creating new data updating existing data deleting existing data