Changes

[maven-release-plugin] prepare release 3.0

[maven-release-plugin] prepare for next development iteration

Corrected link to the spec (#505)

ci: trigger build on pull request (#462)

Signed-off-by: Sean C. Sullivan <github@seansullivan.com>

ci: mvn --no-transfer-progress (#461)

Signed-off-by: Sean C. Sullivan <github@seansullivan.com>

Enable UserResource in airlines app

Currently, the TCK verifies that the implementation creates paths and
operations for UserResource, even though it isn't configured as a rest
resource.

The spec doesn't demand that this should or shouldn't happen and it
makes sense for implementations to be allowed to check which resources
are actually included in the rest application and only generate schema
for those that are.

Support extensions as nested annotations for extensible models

Add TCK test to check nested extension annotation placement/priority

Fixed links to the spec (#511)

* Fixed links to the spec

Signed-off-by: Helber Belmiro <helber.belmiro@gmail.com>

* Corrected link to the spec

Signed-off-by: Helber Belmiro <helber.belmiro@gmail.com>

ci: setup-java v2 (#507)

setup-java v3 (#514)

Add `extensions` to `@Content` and `@APIResponses`, adjust TCK test

JavaDoc improvements

Correct TCK test constants

Update calendar (links for two TZs), update agenda/minutes link

Test default `required` value for each parameter type

update spec regarding cors (#521)

* update spec regarding cors

* Update spec/src/main/asciidoc/microprofile-openapi-spec.asciidoc

Co-authored-by: Michael Edgar <michael@xlate.io>

Co-authored-by: Michael Edgar <michael@xlate.io>

fix the out-of-date version reference (#522)

Don't test format parameter

Remove PetStoreAppTest.testJsonResponseTypeWithQueryParameter because
support for the format parameter is optional.

Allow APIResponse on resource class

APIResponse annotations on the method override APIResponse annotations
on the resource class with the same response code.

Support Schema `additionalProperties` via annotation

Fixes #423

Tests for hidden schemas

* Test that a field annotated with @Schema(hidden = true) is not
  included in the schema for the enclosing class
* Test that a resource method parameter annotated with @QueryParam and
  @Schema(hidden = true) creates a parameter with no schema in the
  openapi document
* Test that a resource method parameter annotated with @Schema(hidden =
  true) creates a request body with no schema in the openapi document

Better support for security requirement objects

* Make SecurityRequirementsSet repeatable
* Add securitySets parameters to OpenAPIDefinition and CallbackOperation
* Clarify that using @SecurityRequirement alone is equivalent to using
@SecurityRequirementsSet with one element
* Add TCK for @SecurityRequirementsSet
* Add TCK for securitySets in @OpenAPIDefinition

Allow APIResponse on ExceptionMapper class

Allow the APIResponse annotation to be used on an exception mapper class
as well as the toResponse method.

Auto-reformat changes from #525

I forgot to allow the auto-formatter to run before submitting that PR

Only require the endpoint under certain conditions

This allows the endpoint not to be served if the user isn't deploying an
application which uses Jakarta RESTful WS and hasn't supplied an OpenAPI
document in another way.

Add a recommended location for any UI

Autoformat

Add Bean Validation integration to spec

- Schema enhanced by certain bean validation annotations
- Can be overridden by user
- Can be disabled by config

TCK tests for Bean Validation integration

Clarify scanning config properties

Define the way that the class scanning inclusion and exclusion
properties work together.

TCKs for class scanning config

Use a dedicated application for class scanning tests to simplify the
tests and allow us to cover more cases.

Create a test utility for setting config properties within a test
application.

Add new TCKs to test the interactions between scanning config
properties.

Convert existing scanning config tests to the same style as the new
tests.

Add missing RunAsClient to BeanValidationTest

Some methods were missing the RunAsClient annotation

Add 3.1 release notes (#536)