Scott M Stark
Scott M Stark
Looking at how the compiler handles imports, it seems that it makes no difference whether a class is explicitly imported or used as a fully qualified type. This means that...
So another workaround that will work for any profile would be to simply attach the jaxb api jar to the test archive using an org.jboss.arquillian.container.test.spi.client.deployment.ApplicationArchiveProcessor implementation. There is an example...
That PR works for WildFly.
@spericas @jansupol We could use an update on this as it is blocking completing the core profile going to ballot.
So at this point a new service release of the tck is needed and a PR to update the jakarta.ee page via the https://github.com/jakartaee/specifications/ repo.
It is fine to merge these as someone with committer access has to approve them. There is never any IP risk associated with this, so just ignore the failed check...
Yes, it is just used to build the aggregate javadoc that go into the apidocs found on the spec page: https://jakarta.ee/specifications/cdi/4.0/apidocs/ I don't really like how this works, but it...
I'm sure it is just a non-critical detail that was not addressed. Maybe it was seen as too self evident to be worth checking.
OK, but could you explain why this is being requested? That header file has been in place since the project inception.