Markus KARG
Markus KARG
### Search first - [X] I searched and no similar issues were found ### Description `generateChangelog` running against SQL Anywhere produces `VARCHAR(n, 1 CHAR)` when it finds a data column...
Closes #4521 ## Impact - [x] Bug fix (non-breaking change which fixes expected existing functionality) - [ ] Enhancement/New feature (adds functionality without impacting existing logic) - [ ] Breaking...
How can I modify the name of the Windows Event Log's **Source**? Apparently the source's name is auto-generated "somehow magically" and I wonder how I can customize that?
### Search first - [X] I searched and no similar issues were found ### Description `generateChangeLog` auto-produces a value for the `author` attribute of the `changeSet` element. While this is...
This Pull Requests proposes an implementation for [JDK-8341566](https://bugs.openjdk.org/browse/JDK-8341566): Adding the new method `public static Reader Reader.of(CharSequence)` will return an anonymous, non-synchronized implementation of a `Reader` for each kind of `CharSequence`...
This PR is a **draft** for further discussion of `ResourceInfo.getAnnotation()`. **It is not intended for code review, voting, or merge.** Please use it solely for discussion, unless we agreed upon...
I hereby propose the addition of the following method: `public A ResourceInfo.getResourceAnnotation(Class annotationClass)` The idea is that this method returns the annotation instance of the given `annotationClass` **with full respect...
# Proposal I like to propose the addition of the new method `MediaType.getCharsetParameter()` which either returns a `Charset` instance, `null`, or throws `UnsupportedCharsetException`. # Justification Rather often I came across...
Recently we deprecated `CacheControl.valueOf(String)`, but the replacement is a rather clumsy code line: `RuntimeDelegate.getInstance().createHeaderDelegate(CacheControl.class).fromString(value)`. This is very annoying e. g. when migrating filters from 2.x to 3.x. To make the...
Each major version of PostgreSQL (in theory) can come with breaking changes in their API and internals. One such breaking change was the **non-optional** addition of ALPN to the TLS...