| Re: [jakartaee-tck-dev] [cu-dev] Concurrency TCK deployed to Maven central and available from download not the same? |
I did not know about this. The Maven Central version should as
you note, have a different license (EPL versus EFTL in
https://download.eclipse.org/...) but otherwise should be exactly
the same. IMO, the only remedy for this is to publish a new
concurrency-tck-3.0.1.zip (or whatever the next version increment
is) to both locations. The EPL TCK can be used for development
purposes and the EFTL TCK should be used in compatibility
certification requests.
Hi,
It looks like the 3.0.0 version of the Concurrency TCK differs functionally (and not just the license) between the version uploaded to Maven Central and to the Eclipse download location (https://download.eclipse.org/jakartaee/concurrency/3.0/concurrency-tck-3.0.0.zip).
The latter seems to cause the following test failure:
ee.jakarta.tck.concurrent.spec.ManagedThreadFactory.resourcedef.ManagedThreadFactoryDefinitionTests.testManagedThreadFactoryDefinitionDefaultsEJB
See
Kind regards,Arjan Tijms
_______________________________________________ cu-dev mailing list cu-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cu-dev