)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…10523)

Fixed #10505

… to v2.0.63.final (#10525)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…lvm.buildtools.native.gradle.plugin to v0.10.1 (#10522)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

… is the separator char (#10516)

* Fix special case of NameUtils.underscoreSeparate where the first char is the separator char results in a double separator char prefix. Also overload the method to support a lowercase result.

fixes #10140

…port-native-io_uring to v0.0.25.final (#10518)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

….4.2 (#10548)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

….4 (#10566)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…tion-bom to v4.4.3 (#10560)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…gradle-plugins to v6.6.4 (#10565)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…solver-core to v3.25.9 (#10571)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…#10583)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* Allow suppressing internal warnings

This PR allows suppressing internal/experimental warnings. In an internal project, this output accounts for ~12% of the whole log, and when you know what you're doing, it's unnecessary.

* Fix Checkstyle

* Use dots

FullNettyHttpClientResponse is modified to copy the source ByteBuf content from
the FullHttpResponse passed to its constructor without increasing the readerIndex
of the source buffer so that it may be re-read upon a creation of a new instance
of FullNettyHttpClientResponse from the same source FullHttpResponse as happens
in the case of a non-error response that fails upon deserialization of the body
content. This ensures that the original body content can still be obtained by
calling HttpClientResponseException.getResponse().getBody(...).

This potentially resolves #10458

… to v2.0.65.final (#10595)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

….4.3 (#10591)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…ind to v2.16.2 (#10594)

see: https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.16.2

When we have a Graal/Kotlin/Maven project we add micronaut-graal to the Kapt annotation processor paths.

When we moved empty arrays to static variables in #10539, we added a requirement for micronaut-core to be also on the classpath.

This PR breaks that requirement, so just adding micronaut-graal to the processors is enough.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

This reverts commit 36ef6b9.

This PR #10597 was an attempt to fix Maven, Graal and Kapt, but it was in error...

The issue wasn't that micronaut-graal was calling micronaut-core.
The issue was that the Kotlin processor had both Micronaut-core 4.3.1 and 4.3.10 in the classpath.

Due to the unique way Maven deals with resolution issues (it just picks the first one it sees), this meant that the processor couldn't see the variables added and renamed in #10539.

And for Kapt, there's nothing we can do to manage this (apart from add every module in micronaut-core to the annotationProcessorPaths).

We are testing fixing it by re-releasing processors with the 4.3.10 version of core.

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

* Handle parsing of form attributes with no value

MicronautHttpData.AttributeImpl is updated to provide an implementation of the setValue method.
This implementation is needed in the corner cases where Netty's HttpPostStandardRequestDecoder
successfully parses an attribute with no value such as in the body "a&b=2".

Tests are added to more thoroughly test the various forms of x-www-form-urlencoded bodies as
specified by https://url.spec.whatwg.org/#application/x-www-form-urlencoded. These tests
include scenarios where we know and expect that HttpPostStandardRequestDecoder will currently
fail to parse an attribute with a name but no value - namely when that attribute is the last
one in a given POST body. If HttpPostStandardRequestDecoder is patched in the future, then
these expected parsing failures can be moved into the success scenario instead.

This partially resolves #10446.

* Use CharSequence version of Unpooled.copiedBuffer

* use BlockingHttpClient

---------

Co-authored-by: Sergio del Amo <sergio.delamo@softamo.com>

…tion-bom to v4.4.4 (#10605)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

…-http3 to v0.0.27.final (#10603)

# Conflicts:
#	.github/workflows/graalvm-dev.yml
#	buildSrc/build.gradle
#	gradle.properties
#	gradle/libs.versions.toml
#	inject-java-test/src/test/groovy/io/micronaut/inject/visitor/beans/BeanIntrospectionSpec.groovy
#	inject/src/main/java/io/micronaut/inject/annotation/AbstractAnnotationMetadata.java
#	settings.gradle