Scott M Stark
Scott M Stark
So the steps involved would be those described in the [Creation Review](https://jakarta.ee/committees/specification/guide/#creation) of the JESP: * Create a Project Proposal[^1]. * Submit a Pull Request to the [Jakarta EE Specifications...
There needs to be a new project created under the https://projects.eclipse.org/projects/ee4j umbrella project. I'll ask the EE4J PMC what needs to be done.
The parent operations guide details the steps for creating a new project: https://www.eclipse.org/projects/efsp/operations.php#efspo-creating I'll start the socialization with the spec committee.
Replaced with #474 since this PR could not be updated via the github interface
This will be dealt with in the new arquillian-jakarta repo
Is there still something to look into here? We are quite far from shinkwrap 2.2.6 now and there have been many changes to the underlying maven libraries at this point.
Done.
> * [ ] Parametrized Arquillian runner: https://github.com/spriadka/testsuite/blob/infinispan-testcase-expansion/common/src/main/java/org/jboss/hal/testsuite/util/junit/ArquillianParametrized.java Is this feature captured by the Junit 5 support and its @ParameterizedTest/@ValueSource annotations? There was just a bug fixed to correct handling...
Let's open more specific issues on the current Junit 5 and CDI support as this does seem addressed at this point.
It is easy enough to add this behavior by adding a rootContext to the HttpContext, but the question is, should it default to "/" or null and keep the current...