Andreas

Hi @bsorrentino, you are using maven-project-info-report:2.4. In the class AbstractProjectInfoReport there is a field called "customBundle", which sadly looks broken in [2.4](https://github.com/apache/maven-project-info-reports-plugin/blob/maven-project-info-reports-plugin-2.4/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java): /** * Path for a custom bundle instead...

Hi @bsorrentino I can't find your 6.10-SNAPSHOT release in Maven Central or your github tags - can you tell me where to find it? Best regards

Hi @bsorrentino thanks, sadly it does not seem to change the behaviour. I added the file _src/site/custom/project-info-reports.properties_ (like specified in [2.9](https://github.com/apache/maven-project-info-reports-plugin/blob/maven-project-info-reports-plugin-2.9/src/main/java/org/apache/maven/report/projectinfo/AbstractProjectInfoReport.java)) to my project and added a custom property: report.team.intro.description1=Something...

I can confirm this bug. Here is my reproducer: ``` {https://docs.github.com/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax "openapi": "3.0.1", "info": { "title": "Reproducer API for missing response schemas", "version": "0.0.1" }, "paths": { "/appointments/{id}": { "get":...

Thank you for our analysis, @tsegismont! I would be a bit sad if you closed this with "won't fix" - as long as the web socket connection is open, it...

Yes `current_schema()` is a bit misleading, although the documentation states it correctly: "Returns the name of the schema that is **first** in the search path" - it does not say...

I'm happy to change it, but this would alter the behavior of the method and might break existing code. Maybe rather update the documentation, that `getSchema()` returns the results of...

> FYI If one of the list items is the special name $user, then the schema having the name returned by CURRENT_USER is substituted, if there is such a schema...

So how do we proceed? My proposal: we keep the PR as it is, `getSchema()` will not be changed. My reasoning behind this is: Currently, if I set multiple schemas...

Ok, I changed `getSchema` to call `SHOW search_path`. I noticed this in a test case: Before (current_schema()): ``` execute("SET search_path TO \"$user\",public,schema2"); assertEquals(TestUtil.getUser(), conn.getSchema()); // Now fails ``` After (show...