-
Different versions of same database platform behave differently, `database-platform` is not enough to choose the most precise dialect, it should combines with `major-version` and `minor-version`, we s…
-
I have been testing `3.8.2-SNAPSHOT` and have observed that after changing server.xml once, further updates to the file are not synch'd up by dev mode.
I ran `mvn liberty:dev` with:
```
jak…
-
To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.
F…
m0mus updated
4 years ago
-
Taking Greg's text from https://github.com/jakartaee/servlet/pull/672 that adds support for early hints.
I understand that this method doesn't change the response headers, but we have other methods…
-
When the platform.artifact=jakarta.platform:jakarta.jakartaee-api:jar:10.0.0-RC1 (Jakarta EE 10 RC1) from the repo.url=https://jakarta.oss.sonatype.org/content/repositories/staging/ (Staging) is confi…
-
**Jetty version(s)**
12.0.8
**Enhancement Description**
If a Servlet is in an active `ReadListener` mode (Async Read), and there is code that attempts to use `ServletInputStream.transferTo()` s…
-
To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.
F…
m0mus updated
4 years ago
-
See https://github.com/jakartaee/jakarta.ee/issues/1505
-
EE 11 caused the integration aspects in the CDI specification to be removed from CDI and placed into platform. Some of them are more logically located in component specifications.
Consider this on…
-
To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.
F…
m0mus updated
4 years ago