Currently, the Servlet TCK jars are only available via a big zip file (https://download.eclipse.org/jakartaee/servlet/6.1/jakarta-servlet-tck-6.1.0.zip). So Maven builds needs to download the zip, extract the jars and then install those in the local repository
While this works, it's not efficient for Maven builds.
We could upload the tck jars to Maven. There is a simple build to do this via Eclipse Jenkins.
Should we push those jars to the groupId: jakarta.tck or jakarta.servlet.tck
@markt-asf any opinion? thanks
Currently, the Servlet TCK jars are only available via a big zip file (https://download.eclipse.org/jakartaee/servlet/6.1/jakarta-servlet-tck-6.1.0.zip). So Maven builds needs to download the zip, extract the jars and then install those in the local repository
While this works, it's not efficient for Maven builds.
We could upload the tck jars to Maven. There is a simple build to do this via Eclipse Jenkins.
Should we push those jars to the groupId:
jakarta.tckorjakarta.servlet.tck@markt-asf any opinion? thanks