Vladimir Sitnikov

I've unified the code and added the description. With those changes, the publish and close tasks would work without any extra info from the user (there's no need to explicitly...

I am afraid we go in circles, and there's no way it could be merged. I would rather close the pr and fork gnpp

What bothers me the most is: * There's virtually no feedback on the high level * https://github.com/gradle-nexus/publish-plugin/pull/145#discussion_r1103829334 * https://github.com/gradle-nexus/publish-plugin/issues/182 -- currently there's no way to execute tests, and there's no...

Incompatible because this component declares a component, compatible with Java 17 and the consumer needed a component, compatible with Java 11

Do we gain much from dropping Java 11? Do we lose userbase by dropping Java 11? I would rather pin mok-oauth2 to v1 to avoid adding unexpected Java 17 requirements...

@sebasbaumh , did you select `Allow edits and access to secrets by maintainers`? I've tried to add a review commit to the branch, however, it says I can't do that....

Probably the last time I spelled the command wrong, it yielded "no permissions", so I assumed edits from maintainers was not enabled.

There's a failure caused by the new code: ``` Suppressed: org.postgresql.util.PSQLException: ERROR: syntax error at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2676) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2366) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:356) at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:496) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:413) at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:190) at org.postgresql.jdbc.TypeInfoCache.getPGType(TypeInfoCache.java:489) at org.postgresql.jdbc.PgConnection.addDataType(PgConnection.java:758)...

`preferQueryMode=simple` can be set for any connection. However, with `simple mode only` binary transfer is not possible anyway, so there's no point in "registering type for binary transfer".

I just realized we should better implement the standard API `java.sql.Connection#setTypeMap(java.util.Map