jstl-api
jstl-api copied to clipboard
tck is using org.eclipse.ee4j as groupId
The tck module is not overriding the groupId if the org.eclipse.ee4j. This does not seem like a valid groupId for a tck.
The current platform-tck release is expecting a jakarta.tck groupId:
<execution>
<id>install-pages-platform-tck</id>
<phase>package</phase>
<goals>
<goal>install-file</goal>
</goals>
<configuration>
<groupId>jakarta.tck</groupId>
<artifactId>pages-platform-tck</artifactId>
<version>${project.version}</version>
<packaging>jar</packaging>
<file>pages-platform-tck-${project.version}.jar</file>
<generatePom>false</generatePom>
</configuration>
</execution>
We will also need a release of the tck staged to include in the candidate platform tck release.
For Jakarta EE11 it looks like the Tags TCK was added back to the platform: https://github.com/jakartaee/platform-tck/pull/1892. For EE12 we need to ensure this is fixed and working correctly.
It was essentially moved back indeed, although the transferred source is still here as well:
https://github.com/jakartaee/tags/tree/master/tck
As soon as EE 11 platform is released we have to delete it once again at the platform-tck and do some updates to the code that resides here.
@arjantijms I see that EE 11 platform is released here: https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-api/11.0.0/
I'm a bit confused -- What exactly needs to be changed here?
Do we need to reintroduce https://github.com/jakartaee/platform-tck/pull/1784?
@arjantijms I see that EE 11 platform is released here: https://repo1.maven.org/maven2/jakarta/platform/jakarta.jakartaee-api/11.0.0/
I'm a bit confused -- What exactly needs to be changed here?
Do we need to reintroduce
https://github.com/jakartaee/platform-tck/pull/1784?
I think that this issue was to ensure the EE 11 Platform TCK release scripts could reference the Tags TCK artifact correctly but I don't think the Platform TCK (EE 12) release script needs to release the Tags 3.1 TCK so no action is needed for this issue.
Sounds fair. I'll close this out. Re-open if anything is needed after all.