Kyle Aure

I did override that method and still got the same `mapped port` error. Here is my test class: https://github.com/KyleAure/WebSphereApps/blob/master/system-test-jdbc/src/test/java/it/io/openliberty/guides/event/Containers.java

## 3.1.0 GA is Staged - GitHub Tag: [3.1.0](https://github.com/jakartaee/concurrency/releases/tag/3.1.0) - GitHub Branch: [RELEASE-3.1.0](https://github.com/jakartaee/concurrency/tree/RELEASE-3.1.0) - GitHub Release DRAFT: [3.1.0](https://github.com/jakartaee/concurrency/releases/edit/untagged-b483f5b2aacccd463566) - Staging Repo: [jakartaenterpriseconcurrent-1018](https://jakarta.oss.sonatype.org/content/repositories/jakartaenterpriseconcurrent-1018/) ## Notes I double checked to make sure...

## 3.1.0 GA is Re-staged - GitHub Tag: [3.1.0](https://github.com/jakartaee/concurrency/releases/tag/3.1.0) - GitHub Branch: [RELEASE-3.1.0](https://github.com/jakartaee/concurrency/tree/RELEASE-3.1.0) - GitHub Release DRAFT: [3.1.0](https://github.com/jakartaee/concurrency/releases/edit/untagged-b483f5b2aacccd463566) - Staging Repo: [jakartaenterpriseconcurrent-1019](https://jakarta.oss.sonatype.org/content/repositories/jakartaenterpriseconcurrent-1019/) ## Verification Data The checksums are as follows:...

Created specification project release review: https://github.com/jakartaee/specifications/pull/733

## 3.1.0 GA is Re-staged - GitHub Tag: [3.1.0](https://github.com/jakartaee/concurrency/releases/tag/3.1.0) - GitHub Branch: [RELEASE-3.1.0](https://github.com/jakartaee/concurrency/tree/RELEASE-3.1.0) - GitHub Release DRAFT: [3.1.0](https://github.com/jakartaee/concurrency/releases/edit/untagged-ce263e2b07b0c4cf451b) - Staging Repo: [jakartaenterpriseconcurrent-1020](https://jakarta.oss.sonatype.org/content/repositories/jakartaenterpriseconcurrent-1020/) - Staged TCK Dist: [concurrency-tck-3.1.0.zip](https://download.eclipse.org/ee4j/cu/jakartaee11/staged/eftl/) ## Verification Data...

Sorry I haven't kept up much with this discussion. I agree with the statement: > it is idiomatic Java if the creator of a "resource", eg. IO stream, is responsible...

@scottmarlow Thanks for the feedback. I was under the impression that this WAS a requirement if we wanted to remove these tests from the Platform TCK project. Is that accurate?...

Awesome thanks for all the feedback @scottmarlow. I'll go ahead and update the mailing list so we can drum up support (or opposition).

It looks like the challenge has been fixed, and these tests are not disabled. Closing as resolved.

Took a look through the repository and all of these dependency issues seem to have been resolved, and we now have dependabot working to keep dependencies up to date.