-
Convert Maven build to gradle
gradle init
-
Initialise new project folder structure (Java example)
gradle init --type java-library
// imports a couple of java tasks | |
apply plugin: "java" | |
// List available tasks in the shell | |
> gradle tasks | |
// A Closure that configures the sourceSets Task | |
// Sets the main folder as Source folder (where the compiler is looking up the .java files) | |
sourceSets { | |
main.java.srcDir "src/main" |
The >>>
operator allows a sequence of values to be returned:
myMock.someCall() >>> ['first value', 'second value', 'third value', 'etc']
This returns each string in turn. Behaviour (such as throwing exceptions) in closures cannot be used by this operator.
The >>
operator allows value or behaviour (closures) to be returned
My aim is to define a set of rules that can be used to decide whether an incremental data change is backwardly compatible or not, list things to beware of for a particular change, and mitigations that can be put in place.
Clearly it is assumed that the services will be using API versioning, and that a major API version number change would allow any required change to that API. The scope of this document is to explore what changes can be made within a single API version.
There are four main release management models, each of which has its own requirements and challenges in versioning the APIs.
Kotlin language website is at https://kotlinlang.org.
All the codes here can be copied and run on Kotlin online editor.
- You do not need
;
to break statements. - Comments are similar to Java or C#,
/* This is comment */
for multi line comments and// for single line comment
.