org.apache.maven.plugin.AbstractMojo; /** * Does nothing. * * @goal it * @requiresDependencyRe compile * * @author Benjamin Bentmann */ public class ItMojo extends AbstractMojo { public void execute() { } } META-INF/maven/org.apache.maven.its.plugins/maven-it-plugin/pom.xml 4.0.0 org.apache.maven.its.plugins maven-it-plugin 0.1 maven-plugin Maven Integration Test Plugin A test plugin to assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api...

org.apache.maven.plugin.AbstractMojo; /** * Does nothing. * * @goal it * @requiresDependencyRe compile * * @author Benjamin Bentmann */ public class ItMojo extends AbstractMojo { public void execute() { } } META-INF/maven/org.apache.maven.its.plugins/maven-it-plugin/pom.xml 4.0.0 org.apache.maven.its.plugins maven-it-plugin 0.1 maven-plugin Maven Integration Test Plugin A test plugin to assist testing of Maven core. 2009 maven-core-it file:///${basedir}/repo true true org.apache.maven maven-plugin-api...

      decompose = {
        listOf(
          it.version,
          it.serialNumber,
          it.signature,
          rdnSequence to it.issuer,
          it.validity,
          rdnSequence to it.subject,
          it.subjectPublicKeyInfo,
          it.issuerUniqueID,
          it.subjectUniqueID,
          it.extensions,
        )
      },
      construct = {

It used custom types in its declarations instead of standard Python types, but it was still a huge step forward.

It also was one of the first frameworks to generate a custom schema declaring the whole API in JSON.

It was not based on a standard like OpenAPI and JSON Schema. So it wouldn't be straightforward to integrate it with other tools, like Swagger UI. But again, it was a very innovative idea.

                        os to (testProject to performanceTestDuration)
                    }
            }
        }
        return pairs.groupBy({ it.first }, { it.second })
            .mapValues { entry -> entry.value.groupBy({ it.first }, { it.second }) }
    }

    private
    fun readPerformanceTestConfigurations(performanceTestsCiJson: File): List<PerformanceTestConfiguration> {

        reports.filter { it.isDirectory }.forEach {
            val destFile = rootBuildDir.resolve("report$projectPathName-${it.name}.zip")
            zip(destFile, it)
        }

        // Zip all files in project build directory into a single zip file to avoid publishing too many tiny files
        reports.filter { it.isFile && it.toPath().startsWith(projectBuildDirPath) }

But all this functionality of using asynchronous code with `async` and `await` is many times summarized as using "coroutines". It is comparable to the main key feature of Go, the "Goroutines".

## Conclusion

    this?.takeIf { it.isNotEmpty() }
        ?.joinToString(separator = ", ", prefix = "<", postfix = ">", transform = transform)
        ?: ""


private
val ApiTypeUsage.isGroovyNamedArgumentMap
    get() = isMap && (
        typeArguments.all { it.isAny }
            || typeArguments.all { it.isStarProjectionTypeUsage }

    You could have custom internal logic to separate it by colon caracters (`:`) or
    similar, and get the two parts `items` and `read`. Many applications do that to
    group and organize permissions, you could do it as well in your application, just
    know that that it is application specific, it's not part of the specification.


    grant_type: the OAuth2 spec says it is required and MUST be the fixed string "password".

            !ignoredSubprojects.contains(it.name)
        }.forEach {
            val dir = File("..", it.path)
            assertEquals(it.unitTests, File(dir, "src/test").isDirectory, "${it.name}'s unitTests is wrong!")
            assertEquals(it.functionalTests, File(dir, "src/integTest").isDirectory, "${it.name}'s functionalTests is wrong!")