* Implement DocumentationProviderFeatures and integrate it in AbstractJavaCodegen
* Integrate DocumentationProviderFeatures in SpringCodegen
* Run new test config spring-boot-springdoc
* Do not use Locale.ROOT
* Do not use Locale.ROOT, use NONE instead of empty list
* Revert "Do not use Locale.ROOT"
This reverts commit a0d6aac92b.
* Do not use forbidden APIs
* Fix spring maven plugin example
* Introduce DocumentationProviderFeaturesTest.java
* replace AUTO with preferredAnnotationLibrary
* remove sout.println from Test
* Apply code style.
* Update spring sample configuration to use the new property
* Update samples after merge
* fix atBean import
* Generate all samples
* Add ParameterObject to test
* Allow Subclasses to opt out
* Use OpenAPI 2 (fka Swagger RESTful API Documentation Specification) instead of just "Swagger"
* export generator docs
* Fix typo
* Fix typo - update docs.
* Created Apache Camel language
* Added unit test
* Fix template dir
* Fix description api
* Camel Dataformat Properties
* Apache Camel Doc
* Apache Camel Doc
* Apache Camel Doc
* Apache Camel maven plugin example
* Fix LOGGER
* Samples
* Camel 3.14
* Samples
* samples
* up to date
* Rename camel to java-camel
* up to date
* Fix SerializedName in modules/openapi-generator/src/main/resources/JavaSpring/pojo.mustache
* Cherry picked commits from add-support-for-collection-of-generic-classes
* Regenerated samples
* Missing work by @adamsz-lume
* Try to fix maven plugin error
Co-authored-by: Bruno Coelho <4brunu@gmail.com>
* [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'
* [java][jersey2-client] Disable coercion of scalars
* Respect the coercion objectmapper setting in deserializers
* Update jackson in maven plugin to get version that has ALLOW_COERCION_OF_SCALARS
* Mustache template should use invokerPackage tag to generate import
* upgrade to http signature library version 1.4
* Use updated HTTP signature library
* Run sample scripts
* Add code samples in README file for HTTP signature
* fix java imports
* Update http-signature version
William Cheng
cachescrubber
Giacomo
Nathan Baulch
Robin Trietsch
Jim Schubert
david1601
Slavek Kabrda
Sebastien Rosset