Fix TCK JavaDoc

[aubi]

Fix javadoc issues.

[KyleAure]

Javadoc changes look good. I'm not sure why we would need to include Transaction as an API dependency. Perhaps others could chime in on that.

[smillidge]

I think it is because it is referenced in the javadoc and now we use modules it is required. @aubi may have more info

[njr-11]

I think it is because it is referenced in the javadoc and now we use modules it is required. @aubi may have more info

It's actually API JavaDoc rather than TCK JavaDoc that references jakarta.transaction, and it's likely my fault from changes introduced in 3.0. In ContextServiceDefinition JavaDoc, it appears that I used {@link jakarta.transaction.UserTransaction} rather than {@code jakarta.transaction.UserTransaction} which is used in the JavaDoc of older code.

You might be able to avoid adding the dependency if you switch that reference.

[arjantijms]

@njr-11 in some of the other specifications we have indeed replaced (or reverted) to using code instead of link. The letter sounds nice in theory, but in practice is unfortunately very troublesome. Maven, let alone java modules, don't have anything like a "doc scope" unfortunately.

[arjantijms]

Transaction requirement should be removed, and we should revert back to code for the javadoc.

[aubi]

@njr-11 @arjantijms @KyleAure @smillidge
Yes, the dependency was because of javadoc link. I changed it to code and removed the dependency on transactions.
I tidied up the commits, so only javadoc fixes and build details remain. Transaction commits were removed.

[arjantijms]

Thx!