feat: exclude the example app from code coverage (ExpediaGroup#297)

Instead of deleting the tests, we can just exclude this project from the reports

fix: allow modifying GraphQLInterfaceType in the willAddGraphQLTypeTo…

…Schema hook (ExpediaGroup#293)

* fix: allow modifying GraphQLInterfaceType in the willAddGraphQLTypeToSchema hook

InterfaceBuilder attempts to create all the implementing `GraphQLObjectType`s after building an interface but before executing the `willAddGraphQLTypeToSchema` hook. This means that if we attempt to update the interface in that hook there could be some objects implementing that interface and referencing the old one. Since graphql-java schema objects don't implement hashcode we end up with type conflict of two interfaces being defined in the schema.

Fix is to use `GraphQLTypeReference` when referencing `GraphQLInterfaceType` from the `GraphQLObjectType` builder. Reference is just by name and they are resolved as the last step of building a schema. This allows us to modify the interface in the hook.

Resolves: ExpediaGroup#281

* update test to verify hook updates interface description

exclude example app from release profile (ExpediaGroup#275)

Based on nexus-staging-maven-plugin it appears that plugin may not release the artifacts if last module (in our case example app) has it disabled. As I workaround I created defaultBuild profile (active by default) that includes example app but if any other profile is specified (e.g. -P release) then default one will be automatically disabled. This will allow us to release only schema generator module.

fix: use maven release plugin in update-version.sh travis script (Exp…

…ediaGroup#273)

versions-maven-plugin is unable to automatically increment snapshot versions of non-standard version project (e.g. 1.0.0-RC1-SNAPSHOT).

fix travis branch regex (ExpediaGroup#265)

Revert throwing exception on missing directive wiring (ExpediaGroup#251)

There are use cases when directives could be just informational (e.g. @deprecated). Instead of defining no-op directive wiring we should just ignore directives without wiring.

Explicit support for deprecated directive in the schema (ExpediaGroup…

…#247)

* Explicit support for deprecated directive in the schema

* custom SDL printer

* customize schema print extension, fix unit tests and detekt

* add printer tests

* revert changes to GraphQLName

example: add another nested example (ExpediaGroup#239)

Update to latest kotlin and fix incorrect jackson version in the exam…

…ple (ExpediaGroup#233)

Typo, "subsciptions" -> "subscriptions" (ExpediaGroup#227)