JSR107 1.1 Maintenance Release Ballot Results

[Greg Luck]

The ballot passed unanimously.

See https://jcp.org/en/jsr/results?id=6087

We will now release.

Greg Luck

[galderz]

Hey Greg,

This is good news.

Looking at Maven, seems like JCache 1.1 API artifacts are there, but the TCK ones are not there yet.

Thoughts?

[Jens Wilke]

On Montag, 18. Dezember 2017 18:14:35 +07 galderz wrote:

> Hey Greg,

>

> This is good news.

>

> Looking at Maven, seems like JCache 1.1 API artifacts are there

> <http://repo1.maven.org/maven2/javax/cache/cache-api/1.1.0/>, but the TCK

> ones are not there <http://repo1.maven.org/maven2/javax/cache/cache-tests/>

> yet.

>

> Thoughts?

 

Hi Galder,

 

actually the license of the TCK 1.1 changed away from Apache, since releasing it under Apache was a mistake. Oracle requires (required?) that the TCK will be distributed via the JCP pages, so that users accept the license terms.

 

The issue is here:

https://github.com/jsr107/jsr107tck/issues/115

 

Maybe this can be reverted somehow under the recent "openess" movement of the EE things.

 

IMHO: An issue against the TCK and some +1s cannot hurt.

 

Best,

 

Jens

 

--

"Everything superfluous is wrong!"

 

// Jens Wilke - headissue GmbH - Germany

\// https://headissue.com

[galderz]

What has license change has to do with publishing artifacts? I don't recall any such discussions on changes to publishing TCK artifacts.

Cheers,

[Jens Wilke]

On Mittwoch, 20. Dezember 2017 00:18:55 +07 galderz wrote:
> What has license change has to do with publishing artifacts? I don't recall
> any such discussions on changes to publishing TCK artifacts.

That was written by Brian Oliver from Oracle in the linked issue:

> That's what we'll do. The TCK download from the JCP will require an executed
SATCK license (at zero cost). That will include the source, compiled binary
and user guide. This way licensees know exactly the version to use for
compliance testing.
> We may keep the source on github public (waiting on confirmation on this),
but implementations claiming TCK compliance will need to license and use the
official TCK.

https://github.com/jsr107/jsr107tck/issues/115#issuecomment-253837877

Maybe that doesn't mean, that the artifacts cannot be published via maven
central as well. However, when including the dependency to the TCK in another
product, it must be dealt somehow with the non Open Source license.

[Greg Luck]

I just published the TCK 1.1 Cache Tests to Maven Central. I had a build issue with the deploy plugin.

I will now publish to spec submit for the click-through.

> On 19 Dec 2017, at 5:21 pm, Jens Wilke <jw_group...@headissue.com> wrote:
>
> On Mittwoch, 20. Dezember 2017 00:18:55 +07 galderz wrote:

>> What has license change has to do with publishing artifacts? I don't recall
>> any such discussions on changes to publishing TCK artifacts.
>

> That was written by Brian Oliver from Oracle in the linked issue:
>
>> That's what we'll do. The TCK download from the JCP will require an executed
> SATCK license (at zero cost). That will include the source, compiled binary
> and user guide. This way licensees know exactly the version to use for
> compliance testing.
>> We may keep the source on github public (waiting on confirmation on this),
> but implementations claiming TCK compliance will need to license and use the
> official TCK.
>
> https://github.com/jsr107/jsr107tck/issues/115#issuecomment-253837877
>
> Maybe that doesn't mean, that the artifacts cannot be published via maven
> central as well. However, when including the dependency to the TCK in another
> product, it must be dealt somehow with the non Open Source license.
>

> Best,
>
> Jens
>
> --
> "Everything superfluous is wrong!"
>
> // Jens Wilke - headissue GmbH - Germany
> \// https://headissue.com
>

> --
> You received this message because you are subscribed to the Google Groups "jsr107" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jsr107+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.