* update to jdk11, fix tests
* update workflow to use jdk11 instead
* update travis, circleci build
* fix test failure, update CI
* skip mvn install in appveyor
* add windows tests
* fix workflow
* remove log level
* add timeout
* sleep more
* skip tests
* sleep more
* only skip tests
* test with jdk11 only
* fix gradlew
* remove skip tests
* start server after build
* update gradle version
* more time to start server
* update to 420
* comment out build
* update
* update
* clean up shippable ci related config and files
* comment out closeAndReleaseRepository
* Revert "comment out closeAndReleaseRepository"
This reverts commit 5a76e403b1419950b229e14199970b2e858da017.
* remove closeAndReleaseRepository
* Upgrade Gradle plugin Gradle build to Gradle 7.5.1
* Update Travis workflow file to support new tasks
* Update Maven POM with Gradle 7.5.1
* Capitalize many occurrences of "Gradle" in the Gradle plugin README
* Update Gradle version in appveyor.yml and shippable.yml
* Update comments
* Update Gradle wrapper to 7.5.1
* Capitalize Gradle in shippable.yml
* Leave Open API
* Upgrade Gradle plugin build to Gradle 7.6
* Upgrade wrapper to Gradle 7.6
* [crystal] update crystal version 1.0.0
* [crystal] show crystal version on CI
* [crystal][client] $ shards update --ignore-crystal-version
* [crystal][client] update pom.xml
* test: enable typescript-axios integration test
* chore: update old dep & devDep
* refactor: use axios installed in test target
* chore(travisCI): update node version from v8.12.0 to v12.20.0
* [maven] Fallback to templates using classpath rather than OS-specific paths
Previous checks would cause logic in Windows to return early, for
built-in templates only. This reorganizes and simplifies the ordering
behavior.
* Match classpath check in WorkflowSettings with that in TemplateManager
* [maven] Much needed unit/integration tests
This follows similar approach used in PMD and other plugins managed by
maven.
Unit tests simply verify we can load configuration as expected into the
Mojo.
Integration tests execute actual sample projects bound to the current
build's Maven plugin. This uses maven-invoker-plugin, which also allows
for specifying the maven options in invoker.properties to execute the test.
It also provides a verification framework using groovy files with the
required naming convention of "verify.groovy". This allows us to quickly
and easily check that certain files are outputted by generation, and we
may also spotcheck file contents.
templateResourcePath option is skipped on windows. I've tested back to
version 3.3.3 and this doesn't seem to have worked consistently with how
the property works on non-Windows.
* Set groovy 3.0.5 for test harness
* Print stacktrace on Maven error in Travis
* [maven] Set groovy version in tests to supported in Java 11+
* Puts maven integration tests in separate profile called 'integration'
* add 'deno' to typescript platforms
* add Deno support to typescript generator
* add Deno support to typescript generator
* add Deno support to typescript generator
* add Deno support to typescript generator
* add Deno support to typescript generator
* add extensionForDeno property for typescript generator
* add URLParse Deno wrapper for typescript generator
* update deno version in .travis.yml
