Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] [cu-dev] Concurrency TCK deployed to Maven central and available from download not the same?
Hi,

I think we should indeed stage and release a 3.0.1 then. I narrowed it down, and the code is indeed different. In particular, this commit is missing from the 3.0.0 download version, but is included in the 3.0.0 maven version:

https://github.com/jakartaee/concurrency/commit/595be6e59dd3f65279db6899c3b9361dd3a160df

Kind regards,
Arjan Tijms


On Fri, Jun 24, 2022 at 3:10 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

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.

On 6/23/22 8:28 PM, arjan tijms wrote:
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

Back to the top