Project Automation
The SORCER Project uses Gradle to automate the building, testing, publishing, deployment of services. Gradle combines the power and flexibility of Ant with the dependency management and conventions of Maven into a more effective way to build. Gradle is powered by a Groovy Domain Specific Language (DSL), Gradle providing a declarative way to describe how the SORCER Project is built, deployed and assembled.
- Consult the Gradle UserGuide
- Consult Gradle DSL documentation
Top Tasks to Remember
Using Gradle with the SORCER Project is easy
-
Lists all available tasks in the current project
gradle tasks
-
Builds the SORCER distribution
gradle distribution
-
Builds the SORCER installer
gradle installer
-
Builds and install project artifacts to the local Maven repository
gradle install
-
Cleans (delete) project artifacts (all output in each project’s build directory)
gradle clean
-
Builds and publish project artifacts to the shared Maven repository
gradle publish
-
Builds and test a project
gradle test
-
Starts the SORCER service browser
gradle browser
-
Starts a provider (from this service provider project)
gradle bootme
-
Stops a provider (from this service provider project)
gradle stopme
-
Starts a requestor (from a service requestor project)
gradle runRequestor
-
Combines starting SORCER and the browser
gradle bootSorcer
gradle bootSorcerRio
-
Combines starting SORCER and the browser
gradle bootSorcer browser
-
Aggregates all tests, view them in build/reports/tests/index.html
gradle allTests
-
Halts SORCER OS Services
gradle terminateSorcer
gradle terminateSorcerRio
-
Generates and aggregates all Java documentation
gradle allJavadoc
Note:
Gradle provides for task shortcuts. What this means is you can use camel-casing to shorth typing a task name to execute. For example:
gradle bootSorcer
Can be shortened to:
gradle bS
Similarly:
gradle runRequestor
Can be shortened to:
gradle rR