You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by Mark Thomas <ma...@apache.org> on 2019/01/18 22:53:08 UTC
Jakarta EE TCKs and compatibility logo
Hi all,
I am writing to your dev@ lists (on BCC) as your project has, in the
past, requested access to the Java EE TCKs while they were controlled by
Sun and then Oracle.
As I am sure you are aware, Java EE has moved to Eclipse and is now
Jakarta EE. The good news is that the TCKs have been open sourced.
https://github.com/eclipse-ee4j/jakartaee-tck
(I haven't tried to build the latest TCK from source yet but it is on my
TODO list.)
Shipping compatible implementations of the Jakarta EE specs (and being
able to make public statements to that effect) will be subject only to
the spec [1] and TCK [2] licenses. There will no longer be a TCK
agreement or NDA to sign. However...
The question has arisen whether or not any ASF projects will want to use
the Jakarta EE compatible logo [3]. If a project wants to be able to do
this, there are some organisational hoops to jump through. Before the
ASF starts down that path the board has asked me to see if there are any
projects that want to use the Jakarta EE compatible logo. After all,
there is no point jumping through the hoops if no-one wants to use the logo.
With the above in mind can you please discuss this amongst your project
community and reply back to jcp-open@apache.org whether or not your
project is interested in being able to use the Jakarta EE compatible
logo. I ask that you complete this no later than the next board meeting
(20th February 2019).
If you have any questions about any of the above, please also use
jcp-open@apache.org to ask them.
Thanks,
Mark
[1] https://www.eclipse.org/legal/efsl.php
[2] https://www.eclipse.org/legal/tck.php
[3] https://www.eclipse.org/legal/tck.php
Re: Jakarta EE TCKs and compatibility logo
Posted by Olivier Lamy <ol...@apache.org>.
I was a bit struggle building it... But ATM I only need binaries so that's
perfect.
Thanks a lot for the informations!
On Mon, 4 Mar 2019 at 19:00, Mark Thomas <ma...@apache.org> wrote:
> On 04/03/2019 08:43, Mark Thomas wrote:
> > On 04/03/2019 08:34, Olivier Lamy wrote:
> >> Hi Mark,
> >> The download link doesn't work (404)
> >
> > Looks like they have moved things around a bit. Try starting from
> > https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/?d
> >
> >> Do you have any idea about how to build or download to execute
> servlet/jsp
> >> tck part?
> >
> > All the notes we have - including known TCK bugs and expected failures
> > are on the wiki
> > https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs
> >
> > The bugs we have reported are getting fixed but those fixes are only
> > going into the master branch not the 8.0.1 branch.
> >
> > I need to go digging to see if I can find a download location for
> > standalone builds for the master branch.
>
> Latest builds of master:
>
> https://jenkins.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run/lastSuccessfulBuild/artifact/standalone-bundles/
>
> From a quick glance, these look to be the Jakarta EE 8 TCKs with the
> various bugs we have reported fixed. I haven't been through a diff
> between master and the EE4J8 branch to confirm that though.
>
> I'm running the TCKs where I'd expect to see fixed bugs now. I'll update
> the wiki with progress.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
On 04/03/2019 08:43, Mark Thomas wrote:
> On 04/03/2019 08:34, Olivier Lamy wrote:
>> Hi Mark,
>> The download link doesn't work (404)
>
> Looks like they have moved things around a bit. Try starting from
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/?d
>
>> Do you have any idea about how to build or download to execute servlet/jsp
>> tck part?
>
> All the notes we have - including known TCK bugs and expected failures
> are on the wiki
> https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs
>
> The bugs we have reported are getting fixed but those fixes are only
> going into the master branch not the 8.0.1 branch.
>
> I need to go digging to see if I can find a download location for
> standalone builds for the master branch.
Latest builds of master:
https://jenkins.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run/lastSuccessfulBuild/artifact/standalone-bundles/
From a quick glance, these look to be the Jakarta EE 8 TCKs with the
various bugs we have reported fixed. I haven't been through a diff
between master and the EE4J8 branch to confirm that though.
I'm running the TCKs where I'd expect to see fixed bugs now. I'll update
the wiki with progress.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
On 04/03/2019 08:34, Olivier Lamy wrote:
> Hi Mark,
> The download link doesn't work (404)
Looks like they have moved things around a bit. Try starting from
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/?d
> Do you have any idea about how to build or download to execute servlet/jsp
> tck part?
All the notes we have - including known TCK bugs and expected failures
are on the wiki
https://cwiki.apache.org/confluence/display/TOMCAT/Jakarta+EE+TCKs
The bugs we have reported are getting fixed but those fixes are only
going into the master branch not the 8.0.1 branch.
I need to go digging to see if I can find a download location for
standalone builds for the master branch.
Mark
> Thanks
> Olivier
>
> On Mon, 18 Feb 2019 at 05:01, Mark Thomas <ma...@apache.org> wrote:
>
>> Ping.
>>
>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>
>> Mark
>>
>> PS If you don't want to build from source, there are nightly TCK builds
>> available here:
>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>
>>
>> On 21/01/2019 10:46, Mark Thomas wrote:
>>> Apologies for the noise.
>>>
>>> The correct link for [3] is:
>>>
>>> https://jakarta.ee/legal/trademark_guidelines/
>>>
>>> I've also corrected a handful of the project BCCs.
>>>
>>> Mark
>>>
>>>
>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>> Hi all,
>>>>
>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>> past, requested access to the Java EE TCKs while they were controlled by
>>>> Sun and then Oracle.
>>>>
>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>
>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>
>>>> (I haven't tried to build the latest TCK from source yet but it is on my
>>>> TODO list.)
>>>>
>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>> able to make public statements to that effect) will be subject only to
>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>> agreement or NDA to sign. However...
>>>>
>>>> The question has arisen whether or not any ASF projects will want to use
>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>>>> this, there are some organisational hoops to jump through. Before the
>>>> ASF starts down that path the board has asked me to see if there are any
>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>> there is no point jumping through the hoops if no-one wants to use the
>> logo.
>>>>
>>>> With the above in mind can you please discuss this amongst your project
>>>> community and reply back to jcp-open@apache.org whether or not your
>>>> project is interested in being able to use the Jakarta EE compatible
>>>> logo. I ask that you complete this no later than the next board meeting
>>>> (20th February 2019).
>>>>
>>>> If you have any questions about any of the above, please also use
>>>> jcp-open@apache.org to ask them.
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>>
>>>>
>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>> [2] https://www.eclipse.org/legal/tck.php
>>>> [3] https://www.eclipse.org/legal/tck.php
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Olivier Lamy <ol...@apache.org>.
Hi Mark,
The download link doesn't work (404)
Do you have any idea about how to build or download to execute servlet/jsp
tck part?
Thanks
Olivier
On Mon, 18 Feb 2019 at 05:01, Mark Thomas <ma...@apache.org> wrote:
> Ping.
>
> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>
> Mark
>
> PS If you don't want to build from source, there are nightly TCK builds
> available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> On 21/01/2019 10:46, Mark Thomas wrote:
> > Apologies for the noise.
> >
> > The correct link for [3] is:
> >
> > https://jakarta.ee/legal/trademark_guidelines/
> >
> > I've also corrected a handful of the project BCCs.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Jakarta EE TCKs and compatibility logo
Posted by Andriy Redko <dr...@gmail.com>.
Hey Colm,
I could take it.
Best Regards,
Andriy Redko
COh> Is anyone interested in taking this on?
COh> Colm.
COh> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>> Ping.
>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>> Mark
>> PS If you don't want to build from source, there are nightly TCK builds
>> available here:
>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>> On 21/01/2019 10:46, Mark Thomas wrote:
>> > Apologies for the noise.
>> >
>> > The correct link for [3] is:
>> >
>> > https://jakarta.ee/legal/trademark_guidelines/
>> >
>> > I've also corrected a handful of the project BCCs.
>> >
>> > Mark
>> >
>> >
>> > On 18/01/2019 22:53, Mark Thomas wrote:
>> >> Hi all,
>> >>
>> >> I am writing to your dev@ lists (on BCC) as your project has, in the
>> >> past, requested access to the Java EE TCKs while they were controlled by
>> >> Sun and then Oracle.
>> >>
>> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> >> Jakarta EE. The good news is that the TCKs have been open sourced.
>> >>
>> >> https://github.com/eclipse-ee4j/jakartaee-tck
>> >>
>> >> (I haven't tried to build the latest TCK from source yet but it is on my
>> >> TODO list.)
>> >>
>> >> Shipping compatible implementations of the Jakarta EE specs (and being
>> >> able to make public statements to that effect) will be subject only to
>> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> >> agreement or NDA to sign. However...
>> >>
>> >> The question has arisen whether or not any ASF projects will want to use
>> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> >> this, there are some organisational hoops to jump through. Before the
>> >> ASF starts down that path the board has asked me to see if there are any
>> >> projects that want to use the Jakarta EE compatible logo. After all,
>> >> there is no point jumping through the hoops if no-one wants to use the
>> logo.
>> >>
>> >> With the above in mind can you please discuss this amongst your project
>> >> community and reply back to jcp-open@apache.org whether or not your
>> >> project is interested in being able to use the Jakarta EE compatible
>> >> logo. I ask that you complete this no later than the next board meeting
>> >> (20th February 2019).
>> >>
>> >> If you have any questions about any of the above, please also use
>> >> jcp-open@apache.org to ask them.
>> >>
>> >> Thanks,
>> >>
>> >> Mark
>> >>
>> >>
>> >> [1] https://www.eclipse.org/legal/efsl.php
>> >> [2] https://www.eclipse.org/legal/tck.php
>> >> [3] https://www.eclipse.org/legal/tck.php
>> >>
>> >
Re: Jakarta EE TCKs and compatibility logo
Posted by Andriy Redko <dr...@gmail.com>.
Hey Colm,
Thanks a lot! Sure, I will do that shortly!
Best Regards,
Andriy Redko
COh> Hi Andriy,
COh> That's fantastic work! Could you capture that information in a wiki?
COh> Colm.
COh> On Thu, Jan 16, 2020 at 1:31 AM Andriy Redko <dr...@gmail.com> wrote:
COh> Hey guys,
COh> Finally, after quite some time, we do have an automated Jenkins job [1] to run
COh> Jakarta RESTful Web Services 2.1 TCK against Apache CXF (literally, any version/PR
COh> but 2.1 compatibility means 3.3.x and above). How does it work (at this moment):
COh> 1) This is parametrized build, needs only CXF version (3.3.4, 3.4.0-SNAPSHOT, or
COh> any custom version available as an artifact in Apache repository). The pipeline does not
COh> build CXF itself (although it could in general, it would take longer). So if you
COh> commit some fixes, please make sure the snapshots/version are published before re-running
COh> the TCK.
COh> 2) The job checks out JakartaEE TCK, builds the JAX-RS TCK only tailored for CXF
COh> (JAX-RS impl classes, etc). We could skip this step when / if official TCKs are
COh> published and become available later on.
COh> 3) The job runs all JAX-RS TCK tests against Glassfish 5.1.0 release
COh> 4) The reports are available as an artifacts [2] (along with JAX-RS TCK distribution)
COh> 5) The pipeline (Jenkins) and parameters are committed to master [3], please feel free to
COh> check and improve it or suggest what you think make sense
COh> 6) The complete run takes around ~2h to complete
COh> 7) Current state [4]:
COh> Tests that passed: 2584
COh> Tests that failed: 77
COh> Tests that had errors: 2
COh> Total: 2663
COh> Some of the fixes are already in PRs state (like SSE fe [5]), others we would need to tackle along the
COh> way, luckily we could track the progress now :-) And we are not that far from getting Jakarta EE TCKs
COh> compatibility logo :)))
COh> Thanks!
COh> [1] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/
COh> [2] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/
COh> [3] https://github.com/apache/cxf/tree/master/tck
COh> [4] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/JTreport/html/report.html
COh> [5] https://github.com/apache/cxf/pull/621
COh> Best Regards,
COh> Andriy Redko
DK>> Consider CXF itself doesn’t even have a real logo, I’m not sure what we’d even do with the compatibility logos. :)
DK>> Anyway, it’s kind of a “nice to have if they become available, but I wouldn’t go out of my way to get them”, IMO.
DK>> Dan
>>> On Feb 27, 2019, at 9:20 PM, Jim Ma <ma...@gmail.com> wrote:
>>> It's a good thing CXF get TCK tests passed. If the logo is not a
>>> complicated thing to request, it's better to have.
>>> Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ?
>>> On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <co...@apache.org>
>>> wrote:
>>>> Is anyone interested in taking this on?
>>>> Colm.
>>>> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>>>>> Ping.
>>>>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>>>> Mark
>>>>> PS If you don't want to build from source, there are nightly TCK builds
>>>>> available here:
>>>>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>>>> On 21/01/2019 10:46, Mark Thomas wrote:
>>>>>> Apologies for the noise.
>>>>>> The correct link for [3] is:
>>>>>> https://jakarta.ee/legal/trademark_guidelines/
>>>>>> I've also corrected a handful of the project BCCs.
>>>>>> Mark
>>>>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>>>>> Hi all,
>>>>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>>>>> past, requested access to the Java EE TCKs while they were controlled
>>>> by
>>>>>>> Sun and then Oracle.
>>>>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>>>> (I haven't tried to build the latest TCK from source yet but it is on
>>>> my
>>>>>>> TODO list.)
>>>>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>>>>> able to make public statements to that effect) will be subject only to
>>>>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>>>>> agreement or NDA to sign. However...
>>>>>>> The question has arisen whether or not any ASF projects will want to
>>>> use
>>>>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to
>>>> do
>>>>>>> this, there are some organisational hoops to jump through. Before the
>>>>>>> ASF starts down that path the board has asked me to see if there are
>>>> any
>>>>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>>>>> there is no point jumping through the hoops if no-one wants to use the
>>>>> logo.
>>>>>>> With the above in mind can you please discuss this amongst your
>>>> project
>>>>>>> community and reply back to jcp-open@apache.org whether or not your
>>>>>>> project is interested in being able to use the Jakarta EE compatible
>>>>>>> logo. I ask that you complete this no later than the next board
>>>> meeting
>>>>>>> (20th February 2019).
>>>>>>> If you have any questions about any of the above, please also use
>>>>>>> jcp-open@apache.org to ask them.
>>>>>>> Thanks,
>>>>>>> Mark
>>>>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>>>>> [2] https://www.eclipse.org/legal/tck.php
>>>>>>> [3] https://www.eclipse.org/legal/tck.php
>>>> --
>>>> Colm O hEigeartaigh
>>>> Talend Community Coder
>>>> http://coders.talend.com
Re: Jakarta EE TCKs and compatibility logo
Posted by Andriy Redko <dr...@gmail.com>.
Hey guys,
Finally found the time to make this change, the pipeline now marks TCK runs as unstable
if some tests are failing [1]. In case someone wants to look on the pipeline itself, it
is part of the repository [2]. Thanks!
[1] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/
[2] https://github.com/apache/cxf/tree/master/tck
Best Regards,
Andriy Redko
DK> Hi Andriy!
>> Done, https://cwiki.apache.org/confluence/display/CXF20DOC/JakartaEE+TCKs, please feel
>> free to check/edit/comment! Thanks!
DK> Great work. I wonder if a Jenkins run with failed TCK tests can be
DK> marked as unstable (yellow) while a failed run (no test execution
DK> possible) is marked as error (red)?
DK> Best,
DK> Dennis
Re: Jakarta EE TCKs and compatibility logo
Posted by Andrey Redko <dr...@gmail.com>.
Hi Dennis,
Yeah, I think we can do that, the TCK build looks pretty reliable but yeah,
we may mark it unstable if only tests fail, thanks!
Best Regards,
Andriy Redko
On Sun, Jan 19, 2020, 5:30 AM Dennis Kieselhorst <ma...@dekies.de> wrote:
> Hi Andriy!
> > Done,
> https://cwiki.apache.org/confluence/display/CXF20DOC/JakartaEE+TCKs,
> please feel
> > free to check/edit/comment! Thanks!
>
> Great work. I wonder if a Jenkins run with failed TCK tests can be
> marked as unstable (yellow) while a failed run (no test execution
> possible) is marked as error (red)?
>
> Best,
>
> Dennis
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Dennis Kieselhorst <ma...@dekies.de>.
Hi Andriy!
> Done, https://cwiki.apache.org/confluence/display/CXF20DOC/JakartaEE+TCKs, please feel
> free to check/edit/comment! Thanks!
Great work. I wonder if a Jenkins run with failed TCK tests can be
marked as unstable (yellow) while a failed run (no test execution
possible) is marked as error (red)?
Best,
Dennis
Re: Jakarta EE TCKs and compatibility logo
Posted by Andriy Redko <dr...@gmail.com>.
Done, https://cwiki.apache.org/confluence/display/CXF20DOC/JakartaEE+TCKs, please feel
free to check/edit/comment! Thanks!
Best Regards,
Andriy Redko
COh> Hi Andriy,
COh> That's fantastic work! Could you capture that information in a wiki?
COh> Colm.
COh> On Thu, Jan 16, 2020 at 1:31 AM Andriy Redko <dr...@gmail.com> wrote:
COh> Hey guys,
COh> Finally, after quite some time, we do have an automated Jenkins job [1] to run
COh> Jakarta RESTful Web Services 2.1 TCK against Apache CXF (literally, any version/PR
COh> but 2.1 compatibility means 3.3.x and above). How does it work (at this moment):
COh> 1) This is parametrized build, needs only CXF version (3.3.4, 3.4.0-SNAPSHOT, or
COh> any custom version available as an artifact in Apache repository). The pipeline does not
COh> build CXF itself (although it could in general, it would take longer). So if you
COh> commit some fixes, please make sure the snapshots/version are published before re-running
COh> the TCK.
COh> 2) The job checks out JakartaEE TCK, builds the JAX-RS TCK only tailored for CXF
COh> (JAX-RS impl classes, etc). We could skip this step when / if official TCKs are
COh> published and become available later on.
COh> 3) The job runs all JAX-RS TCK tests against Glassfish 5.1.0 release
COh> 4) The reports are available as an artifacts [2] (along with JAX-RS TCK distribution)
COh> 5) The pipeline (Jenkins) and parameters are committed to master [3], please feel free to
COh> check and improve it or suggest what you think make sense
COh> 6) The complete run takes around ~2h to complete
COh> 7) Current state [4]:
COh> Tests that passed: 2584
COh> Tests that failed: 77
COh> Tests that had errors: 2
COh> Total: 2663
COh> Some of the fixes are already in PRs state (like SSE fe [5]), others we would need to tackle along the
COh> way, luckily we could track the progress now :-) And we are not that far from getting Jakarta EE TCKs
COh> compatibility logo :)))
COh> Thanks!
COh> [1] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/
COh> [2] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/
COh> [3] https://github.com/apache/cxf/tree/master/tck
COh> [4] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/JTreport/html/report.html
COh> [5] https://github.com/apache/cxf/pull/621
COh> Best Regards,
COh> Andriy Redko
DK>> Consider CXF itself doesn’t even have a real logo, I’m not sure what we’d even do with the compatibility logos. :)
DK>> Anyway, it’s kind of a “nice to have if they become available, but I wouldn’t go out of my way to get them”, IMO.
DK>> Dan
>>> On Feb 27, 2019, at 9:20 PM, Jim Ma <ma...@gmail.com> wrote:
>>> It's a good thing CXF get TCK tests passed. If the logo is not a
>>> complicated thing to request, it's better to have.
>>> Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ?
>>> On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <co...@apache.org>
>>> wrote:
>>>> Is anyone interested in taking this on?
>>>> Colm.
>>>> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>>>>> Ping.
>>>>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>>>> Mark
>>>>> PS If you don't want to build from source, there are nightly TCK builds
>>>>> available here:
>>>>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>>>> On 21/01/2019 10:46, Mark Thomas wrote:
>>>>>> Apologies for the noise.
>>>>>> The correct link for [3] is:
>>>>>> https://jakarta.ee/legal/trademark_guidelines/
>>>>>> I've also corrected a handful of the project BCCs.
>>>>>> Mark
>>>>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>>>>> Hi all,
>>>>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>>>>> past, requested access to the Java EE TCKs while they were controlled
>>>> by
>>>>>>> Sun and then Oracle.
>>>>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>>>> (I haven't tried to build the latest TCK from source yet but it is on
>>>> my
>>>>>>> TODO list.)
>>>>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>>>>> able to make public statements to that effect) will be subject only to
>>>>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>>>>> agreement or NDA to sign. However...
>>>>>>> The question has arisen whether or not any ASF projects will want to
>>>> use
>>>>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to
>>>> do
>>>>>>> this, there are some organisational hoops to jump through. Before the
>>>>>>> ASF starts down that path the board has asked me to see if there are
>>>> any
>>>>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>>>>> there is no point jumping through the hoops if no-one wants to use the
>>>>> logo.
>>>>>>> With the above in mind can you please discuss this amongst your
>>>> project
>>>>>>> community and reply back to jcp-open@apache.org whether or not your
>>>>>>> project is interested in being able to use the Jakarta EE compatible
>>>>>>> logo. I ask that you complete this no later than the next board
>>>> meeting
>>>>>>> (20th February 2019).
>>>>>>> If you have any questions about any of the above, please also use
>>>>>>> jcp-open@apache.org to ask them.
>>>>>>> Thanks,
>>>>>>> Mark
>>>>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>>>>> [2] https://www.eclipse.org/legal/tck.php
>>>>>>> [3] https://www.eclipse.org/legal/tck.php
>>>> --
>>>> Colm O hEigeartaigh
>>>> Talend Community Coder
>>>> http://coders.talend.com
Re: Jakarta EE TCKs and compatibility logo
Posted by Colm O hEigeartaigh <co...@apache.org>.
Hi Andriy,
That's fantastic work! Could you capture that information in a wiki?
Colm.
On Thu, Jan 16, 2020 at 1:31 AM Andriy Redko <dr...@gmail.com> wrote:
> Hey guys,
>
> Finally, after quite some time, we do have an automated Jenkins job [1] to
> run
> Jakarta RESTful Web Services 2.1 TCK against Apache CXF (literally, any
> version/PR
> but 2.1 compatibility means 3.3.x and above). How does it work (at this
> moment):
>
> 1) This is parametrized build, needs only CXF version (3.3.4,
> 3.4.0-SNAPSHOT, or
> any custom version available as an artifact in Apache repository). The
> pipeline does not
> build CXF itself (although it could in general, it would take longer). So
> if you
> commit some fixes, please make sure the snapshots/version are published
> before re-running
> the TCK.
>
> 2) The job checks out JakartaEE TCK, builds the JAX-RS TCK only tailored
> for CXF
> (JAX-RS impl classes, etc). We could skip this step when / if official
> TCKs are
> published and become available later on.
>
> 3) The job runs all JAX-RS TCK tests against Glassfish 5.1.0 release
>
> 4) The reports are available as an artifacts [2] (along with JAX-RS TCK
> distribution)
>
> 5) The pipeline (Jenkins) and parameters are committed to master [3],
> please feel free to
> check and improve it or suggest what you think make sense
>
> 6) The complete run takes around ~2h to complete
>
> 7) Current state [4]:
>
> Tests that passed: 2584
> Tests that failed: 77
> Tests that had errors: 2
> Total: 2663
>
> Some of the fixes are already in PRs state (like SSE fe [5]), others we
> would need to tackle along the
> way, luckily we could track the progress now :-) And we are not that far
> from getting Jakarta EE TCKs
> compatibility logo :)))
>
> Thanks!
>
> [1] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/
> [2]
> https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/
> [3] https://github.com/apache/cxf/tree/master/tck
> [4]
> https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/JTreport/html/report.html
> [5] https://github.com/apache/cxf/pull/621
>
> Best Regards,
> Andriy Redko
>
> DK> Consider CXF itself doesn’t even have a real logo, I’m not sure what
> we’d even do with the compatibility logos. :)
>
> DK> Anyway, it’s kind of a “nice to have if they become available, but I
> wouldn’t go out of my way to get them”, IMO.
>
> DK> Dan
>
>
> >> On Feb 27, 2019, at 9:20 PM, Jim Ma <ma...@gmail.com> wrote:
>
> >> It's a good thing CXF get TCK tests passed. If the logo is not a
> >> complicated thing to request, it's better to have.
> >> Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE
> TCK ?
>
> >> On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <
> coheigea@apache.org>
> >> wrote:
>
> >>> Is anyone interested in taking this on?
>
> >>> Colm.
>
> >>> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>
> >>>> Ping.
>
> >>>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as
> yet.
>
> >>>> Mark
>
> >>>> PS If you don't want to build from source, there are nightly TCK
> builds
> >>>> available here:
> >>>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> >>>> On 21/01/2019 10:46, Mark Thomas wrote:
> >>>>> Apologies for the noise.
>
> >>>>> The correct link for [3] is:
>
> >>>>> https://jakarta.ee/legal/trademark_guidelines/
>
> >>>>> I've also corrected a handful of the project BCCs.
>
> >>>>> Mark
>
>
> >>>>> On 18/01/2019 22:53, Mark Thomas wrote:
> >>>>>> Hi all,
>
> >>>>>> I am writing to your dev@ lists (on BCC) as your project has, in
> the
> >>>>>> past, requested access to the Java EE TCKs while they were
> controlled
> >>> by
> >>>>>> Sun and then Oracle.
>
> >>>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >>>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> >>>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>
> >>>>>> (I haven't tried to build the latest TCK from source yet but it is
> on
> >>> my
> >>>>>> TODO list.)
>
> >>>>>> Shipping compatible implementations of the Jakarta EE specs (and
> being
> >>>>>> able to make public statements to that effect) will be subject only
> to
> >>>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >>>>>> agreement or NDA to sign. However...
>
> >>>>>> The question has arisen whether or not any ASF projects will want to
> >>> use
> >>>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to
> >>> do
> >>>>>> this, there are some organisational hoops to jump through. Before
> the
> >>>>>> ASF starts down that path the board has asked me to see if there are
> >>> any
> >>>>>> projects that want to use the Jakarta EE compatible logo. After all,
> >>>>>> there is no point jumping through the hoops if no-one wants to use
> the
> >>>> logo.
>
> >>>>>> With the above in mind can you please discuss this amongst your
> >>> project
> >>>>>> community and reply back to jcp-open@apache.org whether or not your
> >>>>>> project is interested in being able to use the Jakarta EE compatible
> >>>>>> logo. I ask that you complete this no later than the next board
> >>> meeting
> >>>>>> (20th February 2019).
>
> >>>>>> If you have any questions about any of the above, please also use
> >>>>>> jcp-open@apache.org to ask them.
>
> >>>>>> Thanks,
>
> >>>>>> Mark
>
>
> >>>>>> [1] https://www.eclipse.org/legal/efsl.php
> >>>>>> [2] https://www.eclipse.org/legal/tck.php
> >>>>>> [3] https://www.eclipse.org/legal/tck.php
>
>
>
>
>
> >>> --
> >>> Colm O hEigeartaigh
>
> >>> Talend Community Coder
> >>> http://coders.talend.com
>
>
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Andriy Redko <dr...@gmail.com>.
Hey guys,
Finally, after quite some time, we do have an automated Jenkins job [1] to run
Jakarta RESTful Web Services 2.1 TCK against Apache CXF (literally, any version/PR
but 2.1 compatibility means 3.3.x and above). How does it work (at this moment):
1) This is parametrized build, needs only CXF version (3.3.4, 3.4.0-SNAPSHOT, or
any custom version available as an artifact in Apache repository). The pipeline does not
build CXF itself (although it could in general, it would take longer). So if you
commit some fixes, please make sure the snapshots/version are published before re-running
the TCK.
2) The job checks out JakartaEE TCK, builds the JAX-RS TCK only tailored for CXF
(JAX-RS impl classes, etc). We could skip this step when / if official TCKs are
published and become available later on.
3) The job runs all JAX-RS TCK tests against Glassfish 5.1.0 release
4) The reports are available as an artifacts [2] (along with JAX-RS TCK distribution)
5) The pipeline (Jenkins) and parameters are committed to master [3], please feel free to
check and improve it or suggest what you think make sense
6) The complete run takes around ~2h to complete
7) Current state [4]:
Tests that passed: 2584
Tests that failed: 77
Tests that had errors: 2
Total: 2663
Some of the fixes are already in PRs state (like SSE fe [5]), others we would need to tackle along the
way, luckily we could track the progress now :-) And we are not that far from getting Jakarta EE TCKs
compatibility logo :)))
Thanks!
[1] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/
[2] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/
[3] https://github.com/apache/cxf/tree/master/tck
[4] https://builds.apache.org/view/C/view/Apache%20CXF/job/CXF-JAXRS-TCK/65/artifact/JTreport/html/report.html
[5] https://github.com/apache/cxf/pull/621
Best Regards,
Andriy Redko
DK> Consider CXF itself doesn’t even have a real logo, I’m not sure what we’d even do with the compatibility logos. :)
DK> Anyway, it’s kind of a “nice to have if they become available, but I wouldn’t go out of my way to get them”, IMO.
DK> Dan
>> On Feb 27, 2019, at 9:20 PM, Jim Ma <ma...@gmail.com> wrote:
>> It's a good thing CXF get TCK tests passed. If the logo is not a
>> complicated thing to request, it's better to have.
>> Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ?
>> On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <co...@apache.org>
>> wrote:
>>> Is anyone interested in taking this on?
>>> Colm.
>>> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>>>> Ping.
>>>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>>> Mark
>>>> PS If you don't want to build from source, there are nightly TCK builds
>>>> available here:
>>>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>>> On 21/01/2019 10:46, Mark Thomas wrote:
>>>>> Apologies for the noise.
>>>>> The correct link for [3] is:
>>>>> https://jakarta.ee/legal/trademark_guidelines/
>>>>> I've also corrected a handful of the project BCCs.
>>>>> Mark
>>>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>>>> Hi all,
>>>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>>>> past, requested access to the Java EE TCKs while they were controlled
>>> by
>>>>>> Sun and then Oracle.
>>>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>>> (I haven't tried to build the latest TCK from source yet but it is on
>>> my
>>>>>> TODO list.)
>>>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>>>> able to make public statements to that effect) will be subject only to
>>>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>>>> agreement or NDA to sign. However...
>>>>>> The question has arisen whether or not any ASF projects will want to
>>> use
>>>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to
>>> do
>>>>>> this, there are some organisational hoops to jump through. Before the
>>>>>> ASF starts down that path the board has asked me to see if there are
>>> any
>>>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>>>> there is no point jumping through the hoops if no-one wants to use the
>>>> logo.
>>>>>> With the above in mind can you please discuss this amongst your
>>> project
>>>>>> community and reply back to jcp-open@apache.org whether or not your
>>>>>> project is interested in being able to use the Jakarta EE compatible
>>>>>> logo. I ask that you complete this no later than the next board
>>> meeting
>>>>>> (20th February 2019).
>>>>>> If you have any questions about any of the above, please also use
>>>>>> jcp-open@apache.org to ask them.
>>>>>> Thanks,
>>>>>> Mark
>>>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>>>> [2] https://www.eclipse.org/legal/tck.php
>>>>>> [3] https://www.eclipse.org/legal/tck.php
>>> --
>>> Colm O hEigeartaigh
>>> Talend Community Coder
>>> http://coders.talend.com
Re: Jakarta EE TCKs and compatibility logo
Posted by Daniel Kulp <dk...@apache.org>.
Consider CXF itself doesn’t even have a real logo, I’m not sure what we’d even do with the compatibility logos. :)
Anyway, it’s kind of a “nice to have if they become available, but I wouldn’t go out of my way to get them”, IMO.
Dan
> On Feb 27, 2019, at 9:20 PM, Jim Ma <ma...@gmail.com> wrote:
>
> It's a good thing CXF get TCK tests passed. If the logo is not a
> complicated thing to request, it's better to have.
> Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ?
>
> On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <co...@apache.org>
> wrote:
>
>> Is anyone interested in taking this on?
>>
>> Colm.
>>
>> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>>
>>> Ping.
>>>
>>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>>
>>> Mark
>>>
>>> PS If you don't want to build from source, there are nightly TCK builds
>>> available here:
>>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>>
>>>
>>> On 21/01/2019 10:46, Mark Thomas wrote:
>>>> Apologies for the noise.
>>>>
>>>> The correct link for [3] is:
>>>>
>>>> https://jakarta.ee/legal/trademark_guidelines/
>>>>
>>>> I've also corrected a handful of the project BCCs.
>>>>
>>>> Mark
>>>>
>>>>
>>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>>> Hi all,
>>>>>
>>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>>> past, requested access to the Java EE TCKs while they were controlled
>> by
>>>>> Sun and then Oracle.
>>>>>
>>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>>
>>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>>
>>>>> (I haven't tried to build the latest TCK from source yet but it is on
>> my
>>>>> TODO list.)
>>>>>
>>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>>> able to make public statements to that effect) will be subject only to
>>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>>> agreement or NDA to sign. However...
>>>>>
>>>>> The question has arisen whether or not any ASF projects will want to
>> use
>>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to
>> do
>>>>> this, there are some organisational hoops to jump through. Before the
>>>>> ASF starts down that path the board has asked me to see if there are
>> any
>>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>>> there is no point jumping through the hoops if no-one wants to use the
>>> logo.
>>>>>
>>>>> With the above in mind can you please discuss this amongst your
>> project
>>>>> community and reply back to jcp-open@apache.org whether or not your
>>>>> project is interested in being able to use the Jakarta EE compatible
>>>>> logo. I ask that you complete this no later than the next board
>> meeting
>>>>> (20th February 2019).
>>>>>
>>>>> If you have any questions about any of the above, please also use
>>>>> jcp-open@apache.org to ask them.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mark
>>>>>
>>>>>
>>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>>> [2] https://www.eclipse.org/legal/tck.php
>>>>> [3] https://www.eclipse.org/legal/tck.php
>>>>>
>>>>
>>>
>>>
>>
>> --
>> Colm O hEigeartaigh
>>
>> Talend Community Coder
>> http://coders.talend.com
>>
--
Daniel Kulp
dkulp@apache.org <ma...@apache.org> - http://dankulp.com/blog <http://dankulp.com/blog>
Talend Community Coder - http://talend.com <http://coders.talend.com/>
Re: Jakarta EE TCKs and compatibility logo
Posted by Jim Ma <ma...@gmail.com>.
It's a good thing CXF get TCK tests passed. If the logo is not a
complicated thing to request, it's better to have.
Do we only need to pass standalone JAXWS and JAXRS TCK instead of EE TCK ?
On Thu, Feb 28, 2019 at 7:29 AM Colm O hEigeartaigh <co...@apache.org>
wrote:
> Is anyone interested in taking this on?
>
> Colm.
>
> On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
>
> > Ping.
> >
> > Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
> >
> > Mark
> >
> > PS If you don't want to build from source, there are nightly TCK builds
> > available here:
> > https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
> >
> >
> > On 21/01/2019 10:46, Mark Thomas wrote:
> > > Apologies for the noise.
> > >
> > > The correct link for [3] is:
> > >
> > > https://jakarta.ee/legal/trademark_guidelines/
> > >
> > > I've also corrected a handful of the project BCCs.
> > >
> > > Mark
> > >
> > >
> > > On 18/01/2019 22:53, Mark Thomas wrote:
> > >> Hi all,
> > >>
> > >> I am writing to your dev@ lists (on BCC) as your project has, in the
> > >> past, requested access to the Java EE TCKs while they were controlled
> by
> > >> Sun and then Oracle.
> > >>
> > >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> > >> Jakarta EE. The good news is that the TCKs have been open sourced.
> > >>
> > >> https://github.com/eclipse-ee4j/jakartaee-tck
> > >>
> > >> (I haven't tried to build the latest TCK from source yet but it is on
> my
> > >> TODO list.)
> > >>
> > >> Shipping compatible implementations of the Jakarta EE specs (and being
> > >> able to make public statements to that effect) will be subject only to
> > >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> > >> agreement or NDA to sign. However...
> > >>
> > >> The question has arisen whether or not any ASF projects will want to
> use
> > >> the Jakarta EE compatible logo [3]. If a project wants to be able to
> do
> > >> this, there are some organisational hoops to jump through. Before the
> > >> ASF starts down that path the board has asked me to see if there are
> any
> > >> projects that want to use the Jakarta EE compatible logo. After all,
> > >> there is no point jumping through the hoops if no-one wants to use the
> > logo.
> > >>
> > >> With the above in mind can you please discuss this amongst your
> project
> > >> community and reply back to jcp-open@apache.org whether or not your
> > >> project is interested in being able to use the Jakarta EE compatible
> > >> logo. I ask that you complete this no later than the next board
> meeting
> > >> (20th February 2019).
> > >>
> > >> If you have any questions about any of the above, please also use
> > >> jcp-open@apache.org to ask them.
> > >>
> > >> Thanks,
> > >>
> > >> Mark
> > >>
> > >>
> > >> [1] https://www.eclipse.org/legal/efsl.php
> > >> [2] https://www.eclipse.org/legal/tck.php
> > >> [3] https://www.eclipse.org/legal/tck.php
> > >>
> > >
> >
> >
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Colm O hEigeartaigh <co...@apache.org>.
Is anyone interested in taking this on?
Colm.
On Sun, Feb 17, 2019 at 7:01 PM Mark Thomas <ma...@apache.org> wrote:
> Ping.
>
> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>
> Mark
>
> PS If you don't want to build from source, there are nightly TCK builds
> available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> On 21/01/2019 10:46, Mark Thomas wrote:
> > Apologies for the noise.
> >
> > The correct link for [3] is:
> >
> > https://jakarta.ee/legal/trademark_guidelines/
> >
> > I've also corrected a handful of the project BCCs.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >
>
>
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Jakarta EE TCKs and compatibility logo
Posted by Robbie Gemmell <ro...@gmail.com>.
On Mon, 18 Feb 2019 at 22:27, Mark Thomas <ma...@apache.org> wrote:
>
> On 18/02/2019 13:43, Oleksandr Rudyy wrote:
<snip>
> > So, in general, I would like to continue running TCK tests with Qpid JMS
> > clients and Qpid Broker-J using Jakarta EE bundle.
> > If Jakarta EE compatible logo is required to add to Qpid Project, I
> > suppose, we can add it.
>
> There is no such requirement. The Jakarta EE compatible logo is
> something Qpid can choose to use - or not - as they wish. There is no
> requirement to use the logo if you run the TCK.
>
That was my reading of the initial mail. I cant speak for anyone else,
but I dont have a particular desire to use the logo.
<snip>
<
> Kind regards,
>
> Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Robbie Gemmell <ro...@gmail.com>.
On Mon, 18 Feb 2019 at 22:27, Mark Thomas <ma...@apache.org> wrote:
>
> On 18/02/2019 13:43, Oleksandr Rudyy wrote:
<snip>
> > So, in general, I would like to continue running TCK tests with Qpid JMS
> > clients and Qpid Broker-J using Jakarta EE bundle.
> > If Jakarta EE compatible logo is required to add to Qpid Project, I
> > suppose, we can add it.
>
> There is no such requirement. The Jakarta EE compatible logo is
> something Qpid can choose to use - or not - as they wish. There is no
> requirement to use the logo if you run the TCK.
>
That was my reading of the initial mail. I cant speak for anyone else,
but I dont have a particular desire to use the logo.
<snip>
<
> Kind regards,
>
> Mark
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
On 18/02/2019 13:43, Oleksandr Rudyy wrote:
> Hi Mark,
>
> I believe that Qpid Team members requested an access to TCK earlier in
> order to test compatibility of Qpid JMS clients with JMS specs.
> We added maven module [1] to run TCK tests against Qpid Broker-J.
> Though, TCK is not part of Qprid Broker-J project and it has to be
> provided externally.
> The TCK bundles need to be downloaded separately and the path to the TCK
> folder needs to be specified to the maven build as JVM property.
> Both TCK tests for JMS 1.1 and JMS 2.0 can be run. However, currently,
> only older Oracle proprietary TCKs are supported due to hard-coded paths
> to the dependency jars.
>
> In order to run TCK tests with new Jakarta EE bundle, the maven profile
> settings needs to be amended. I will change that later.
>
> So, in general, I would like to continue running TCK tests with Qpid JMS
> clients and Qpid Broker-J using Jakarta EE bundle.
> If Jakarta EE compatible logo is required to add to Qpid Project, I
> suppose, we can add it.
There is no such requirement. The Jakarta EE compatible logo is
something Qpid can choose to use - or not - as they wish. There is no
requirement to use the logo if you run the TCK.
> Mark,
> Do you know whether there are any plans to release TCK bundles into
> maven repository?
I don't.
> I suppose that JMS 1.1 TCK is not supported by Jakarta EE and if I still
> want to run JMS 1.1 TCK I need to use Oracle provided bundle.
Correct. None of the history of Java EE was imported into Jakarta EE -
just the current state of the point Java EE 8 was released - so it isn't
possible to re-create any earlier versions.
Kind regards,
Mark
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
On 18/02/2019 13:43, Oleksandr Rudyy wrote:
> Hi Mark,
>
> I believe that Qpid Team members requested an access to TCK earlier in
> order to test compatibility of Qpid JMS clients with JMS specs.
> We added maven module [1] to run TCK tests against Qpid Broker-J.
> Though, TCK is not part of Qprid Broker-J project and it has to be
> provided externally.
> The TCK bundles need to be downloaded separately and the path to the TCK
> folder needs to be specified to the maven build as JVM property.
> Both TCK tests for JMS 1.1 and JMS 2.0 can be run. However, currently,
> only older Oracle proprietary TCKs are supported due to hard-coded paths
> to the dependency jars.
>
> In order to run TCK tests with new Jakarta EE bundle, the maven profile
> settings needs to be amended. I will change that later.
>
> So, in general, I would like to continue running TCK tests with Qpid JMS
> clients and Qpid Broker-J using Jakarta EE bundle.
> If Jakarta EE compatible logo is required to add to Qpid Project, I
> suppose, we can add it.
There is no such requirement. The Jakarta EE compatible logo is
something Qpid can choose to use - or not - as they wish. There is no
requirement to use the logo if you run the TCK.
> Mark,
> Do you know whether there are any plans to release TCK bundles into
> maven repository?
I don't.
> I suppose that JMS 1.1 TCK is not supported by Jakarta EE and if I still
> want to run JMS 1.1 TCK I need to use Oracle provided bundle.
Correct. None of the history of Java EE was imported into Jakarta EE -
just the current state of the point Java EE 8 was released - so it isn't
possible to re-create any earlier versions.
Kind regards,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Oleksandr Rudyy <or...@gmail.com>.
Hi Mark,
I believe that Qpid Team members requested an access to TCK earlier in
order to test compatibility of Qpid JMS clients with JMS specs.
We added maven module [1] to run TCK tests against Qpid Broker-J. Though,
TCK is not part of Qprid Broker-J project and it has to be provided
externally.
The TCK bundles need to be downloaded separately and the path to the TCK
folder needs to be specified to the maven build as JVM property.
Both TCK tests for JMS 1.1 and JMS 2.0 can be run. However, currently, only
older Oracle proprietary TCKs are supported due to hard-coded paths to the
dependency jars.
In order to run TCK tests with new Jakarta EE bundle, the maven profile
settings needs to be amended. I will change that later.
So, in general, I would like to continue running TCK tests with Qpid JMS
clients and Qpid Broker-J using Jakarta EE bundle.
If Jakarta EE compatible logo is required to add to Qpid Project, I
suppose, we can add it.
Mark,
Do you know whether there are any plans to release TCK bundles into maven
repository?
I suppose that JMS 1.1 TCK is not supported by Jakarta EE and if I still
want to run JMS 1.1 TCK I need to use Oracle provided bundle.
Kind Regards,
Alex
[1]
https://cwiki.apache.org/confluence/display/qpid/How+To+Build+Qpid+Broker-J#HowToBuildQpidBroker-J-JMSTCK
On Sun, 17 Feb 2019 at 19:01, Mark Thomas <ma...@apache.org> wrote:
> Ping.
>
> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>
> Mark
>
> PS If you don't want to build from source, there are nightly TCK builds
> available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> On 21/01/2019 10:46, Mark Thomas wrote:
> > Apologies for the noise.
> >
> > The correct link for [3] is:
> >
> > https://jakarta.ee/legal/trademark_guidelines/
> >
> > I've also corrected a handful of the project BCCs.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Rob Tompkins <ch...@gmail.com>.
I’m uncertain here.
-Rob
> On Feb 18, 2019, at 10:42 AM, Benedikt Ritter <br...@apache.org> wrote:
>
> Hi,
>
> Which of our components implement Java EE APIs? I see:
>
> - BSF: not sure anybody is actively working on this
> - JCS: I've seen some activity
>
> Anything else?
>
> Benedikt
>
> Am So., 17. Feb. 2019 um 20:01 Uhr schrieb Mark Thomas <ma...@apache.org>:
>
>> Ping.
>>
>> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>>
>> Mark
>>
>> PS If you don't want to build from source, there are nightly TCK builds
>> available here:
>> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>>
>>
>> On 21/01/2019 10:46, Mark Thomas wrote:
>>> Apologies for the noise.
>>>
>>> The correct link for [3] is:
>>>
>>> https://jakarta.ee/legal/trademark_guidelines/
>>>
>>> I've also corrected a handful of the project BCCs.
>>>
>>> Mark
>>>
>>>
>>> On 18/01/2019 22:53, Mark Thomas wrote:
>>>> Hi all,
>>>>
>>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>>> past, requested access to the Java EE TCKs while they were controlled by
>>>> Sun and then Oracle.
>>>>
>>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>>
>>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>>
>>>> (I haven't tried to build the latest TCK from source yet but it is on my
>>>> TODO list.)
>>>>
>>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>>> able to make public statements to that effect) will be subject only to
>>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>>> agreement or NDA to sign. However...
>>>>
>>>> The question has arisen whether or not any ASF projects will want to use
>>>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>>>> this, there are some organisational hoops to jump through. Before the
>>>> ASF starts down that path the board has asked me to see if there are any
>>>> projects that want to use the Jakarta EE compatible logo. After all,
>>>> there is no point jumping through the hoops if no-one wants to use the
>> logo.
>>>>
>>>> With the above in mind can you please discuss this amongst your project
>>>> community and reply back to jcp-open@apache.org whether or not your
>>>> project is interested in being able to use the Jakarta EE compatible
>>>> logo. I ask that you complete this no later than the next board meeting
>>>> (20th February 2019).
>>>>
>>>> If you have any questions about any of the above, please also use
>>>> jcp-open@apache.org to ask them.
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>>
>>>>
>>>> [1] https://www.eclipse.org/legal/efsl.php
>>>> [2] https://www.eclipse.org/legal/tck.php
>>>> [3] https://www.eclipse.org/legal/tck.php
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Benedikt Ritter <br...@apache.org>.
Hi,
Which of our components implement Java EE APIs? I see:
- BSF: not sure anybody is actively working on this
- JCS: I've seen some activity
Anything else?
Benedikt
Am So., 17. Feb. 2019 um 20:01 Uhr schrieb Mark Thomas <ma...@apache.org>:
> Ping.
>
> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>
> Mark
>
> PS If you don't want to build from source, there are nightly TCK builds
> available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> On 21/01/2019 10:46, Mark Thomas wrote:
> > Apologies for the noise.
> >
> > The correct link for [3] is:
> >
> > https://jakarta.ee/legal/trademark_guidelines/
> >
> > I've also corrected a handful of the project BCCs.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Oleksandr Rudyy <or...@gmail.com>.
Hi Mark,
I believe that Qpid Team members requested an access to TCK earlier in
order to test compatibility of Qpid JMS clients with JMS specs.
We added maven module [1] to run TCK tests against Qpid Broker-J. Though,
TCK is not part of Qprid Broker-J project and it has to be provided
externally.
The TCK bundles need to be downloaded separately and the path to the TCK
folder needs to be specified to the maven build as JVM property.
Both TCK tests for JMS 1.1 and JMS 2.0 can be run. However, currently, only
older Oracle proprietary TCKs are supported due to hard-coded paths to the
dependency jars.
In order to run TCK tests with new Jakarta EE bundle, the maven profile
settings needs to be amended. I will change that later.
So, in general, I would like to continue running TCK tests with Qpid JMS
clients and Qpid Broker-J using Jakarta EE bundle.
If Jakarta EE compatible logo is required to add to Qpid Project, I
suppose, we can add it.
Mark,
Do you know whether there are any plans to release TCK bundles into maven
repository?
I suppose that JMS 1.1 TCK is not supported by Jakarta EE and if I still
want to run JMS 1.1 TCK I need to use Oracle provided bundle.
Kind Regards,
Alex
[1]
https://cwiki.apache.org/confluence/display/qpid/How+To+Build+Qpid+Broker-J#HowToBuildQpidBroker-J-JMSTCK
On Sun, 17 Feb 2019 at 19:01, Mark Thomas <ma...@apache.org> wrote:
> Ping.
>
> Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
>
> Mark
>
> PS If you don't want to build from source, there are nightly TCK builds
> available here:
> https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
>
>
> On 21/01/2019 10:46, Mark Thomas wrote:
> > Apologies for the noise.
> >
> > The correct link for [3] is:
> >
> > https://jakarta.ee/legal/trademark_guidelines/
> >
> > I've also corrected a handful of the project BCCs.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
> For additional commands, e-mail: dev-help@qpid.apache.org
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@axis.apache.org
For additional commands, e-mail: general-help@axis.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Jeff Genender <jg...@apache.org>.
Do we really need it? no.
Is it good for marketing? yes.
I would tend to +1 getting the logo. I know during the big Sun JavaEE days, that logo was a big deal to have.
Jeff
> On Jan 21, 2019, at 12:25 PM, Dennis Kieselhorst <de...@apache.org> wrote:
>
> Hi,
>
> I think we should definitely setup jobs to ensure the TCKs pass but do we really need the logo?! What do you think?
>
> Cheers
> Dennis
>
> On 2019/01/21 10:46:37, Mark Thomas <ma...@apache.org> wrote:
>> Apologies for the noise.
>>
>> The correct link for [3] is:
>>
>> https://jakarta.ee/legal/trademark_guidelines/
>>
>> I've also corrected a handful of the project BCCs.
>>
>> Mark
>>
>>
>> On 18/01/2019 22:53, Mark Thomas wrote:
>>> Hi all,
>>>
>>> I am writing to your dev@ lists (on BCC) as your project has, in the
>>> past, requested access to the Java EE TCKs while they were controlled by
>>> Sun and then Oracle.
>>>
>>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>>
>>> https://github.com/eclipse-ee4j/jakartaee-tck
>>>
>>> (I haven't tried to build the latest TCK from source yet but it is on my
>>> TODO list.)
>>>
>>> Shipping compatible implementations of the Jakarta EE specs (and being
>>> able to make public statements to that effect) will be subject only to
>>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>>> agreement or NDA to sign. However...
>>>
>>> The question has arisen whether or not any ASF projects will want to use
>>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>>> this, there are some organisational hoops to jump through. Before the
>>> ASF starts down that path the board has asked me to see if there are any
>>> projects that want to use the Jakarta EE compatible logo. After all,
>>> there is no point jumping through the hoops if no-one wants to use the logo.
>>>
>>> With the above in mind can you please discuss this amongst your project
>>> community and reply back to jcp-open@apache.org whether or not your
>>> project is interested in being able to use the Jakarta EE compatible
>>> logo. I ask that you complete this no later than the next board meeting
>>> (20th February 2019).
>>>
>>> If you have any questions about any of the above, please also use
>>> jcp-open@apache.org to ask them.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>>
>>> [1] https://www.eclipse.org/legal/efsl.php
>>> [2] https://www.eclipse.org/legal/tck.php
>>> [3] https://www.eclipse.org/legal/tck.php
>>>
>>
>>
Re: Jakarta EE TCKs and compatibility logo
Posted by Dennis Kieselhorst <de...@apache.org>.
Hi,
I think we should definitely setup jobs to ensure the TCKs pass but do we really need the logo?! What do you think?
Cheers
Dennis
On 2019/01/21 10:46:37, Mark Thomas <ma...@apache.org> wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
> > Hi all,
> >
> > I am writing to your dev@ lists (on BCC) as your project has, in the
> > past, requested access to the Java EE TCKs while they were controlled by
> > Sun and then Oracle.
> >
> > As I am sure you are aware, Java EE has moved to Eclipse and is now
> > Jakarta EE. The good news is that the TCKs have been open sourced.
> >
> > https://github.com/eclipse-ee4j/jakartaee-tck
> >
> > (I haven't tried to build the latest TCK from source yet but it is on my
> > TODO list.)
> >
> > Shipping compatible implementations of the Jakarta EE specs (and being
> > able to make public statements to that effect) will be subject only to
> > the spec [1] and TCK [2] licenses. There will no longer be a TCK
> > agreement or NDA to sign. However...
> >
> > The question has arisen whether or not any ASF projects will want to use
> > the Jakarta EE compatible logo [3]. If a project wants to be able to do
> > this, there are some organisational hoops to jump through. Before the
> > ASF starts down that path the board has asked me to see if there are any
> > projects that want to use the Jakarta EE compatible logo. After all,
> > there is no point jumping through the hoops if no-one wants to use the logo.
> >
> > With the above in mind can you please discuss this amongst your project
> > community and reply back to jcp-open@apache.org whether or not your
> > project is interested in being able to use the Jakarta EE compatible
> > logo. I ask that you complete this no later than the next board meeting
> > (20th February 2019).
> >
> > If you have any questions about any of the above, please also use
> > jcp-open@apache.org to ask them.
> >
> > Thanks,
> >
> > Mark
> >
> >
> > [1] https://www.eclipse.org/legal/efsl.php
> > [2] https://www.eclipse.org/legal/tck.php
> > [3] https://www.eclipse.org/legal/tck.php
> >
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Ping.
Just a gentle reminder as I haven't seen any emails to jcp-open@ as yet.
Mark
PS If you don't want to build from source, there are nightly TCK builds
available here:
https://download.eclipse.org/ee4j/jakartaee-tck/8.0.1/nightly/
On 21/01/2019 10:46, Mark Thomas wrote:
> Apologies for the noise.
>
> The correct link for [3] is:
>
> https://jakarta.ee/legal/trademark_guidelines/
>
> I've also corrected a handful of the project BCCs.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@axis.apache.org
For additional commands, e-mail: general-help@axis.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Sam Ruby <ru...@intertwingly.net>.
Feeling a bit nostalgic, I took a peek. Other than offering to sign
on specific piece, I'm not writing this with any particular hat on,
other than perhaps being one of the members of the legal affairs
committee.
TL;DR: my read is that yes we can get a free Associate Membership, but
that doesn't give us what we want/need. Other levels of membership
require fees, and that is a non-starter. Please let me know if I'm
reading this wrong.
All things considered, this appears to be a considerably better
starting position than we ever got from Sun or Oracle, and if Eclipse
is willing to consider a few changes/clarifications, perhaps we can
find a way to make it work.
On Thu, Mar 28, 2019 at 4:48 PM David Blevins <da...@gmail.com> wrote:
>
> Following up on some offline threads. High level status of the steps and progress.
>
> 1. We join the Eclipse Foundation as a n on-voting Associate Member ($0) -
> the Membership Agreement and Membership Application are both here
> <https://www.eclipse.org/membership/become_a_member/>
>
> [in review?]
The agreement seems innocuous. We provide organizational information
(essentially a mailing address), the name of a company representative,
marketing representative, and a billing contact (presumably
non-applicable, but we can certainly provide a contact at Virtual),
and indicate that we are a "Non-Profit Open Source Organization".
Nothing concerning here.
The key agreement is section D, and I don't see any problems there either:
"As a new member we agree to publicly announce that we have joined the
Eclipse Foundation, Inc.
As a Member of Eclipse Foundation we agree to provide Eclipse
Foundation with a logo (or directions to obtain a logo) for the
Foundation’s use in recognizing Member’s relationship with the Eclipse
Foundation. See
https://www.eclipse.org/membership/exploreMembership.php for a full
list of members."
So, +1 on signing this. At the moment, we don't have a designated
officer dedicated to this role. If there are no objections, I'm
willing to sign this on the ASF's behalf. If there are objections or
somebody feels that they should be the one to sign, I would defer to
them.
> 2. A Jakarta EE WG member nominates the ASF as a Guest Member of the working
> group. Guest Members must be voted in by the Jakarta EE Steering
> Committee, and re-approved annually.
>
> [done]
>
> 3. We join the Jakarta EE Working Group as a Guest
> Member which will require signing the Working Group
> Participation Agreement. The current version of the agreement is
> listed under Related Links here
> <https://www.eclipse.org/org/workinggroups/about.php> and
> requires execution of the main agreement and Exhibit J.
>
> [in review?]
The bulk of this agreement seems to resolve around fees. If our fees
are non-zero, that's a deal breaker. If our fees are zero, much of
this agreement is non-applicable. Along these lines, I have
significant concern about section 3. My read is that as an open
source organization we can get an Affiliate membership, but such does
not get us a seat in a working group. The agreement to join the
working group requires us to up our membership to the Solutions
member, which is not made available for free. It also requires us to
make a commercial Eclipse-based offering within 12 months.
There is a section (7) which mentions that we may get working group
private and re-distributable binary materials. I'm OK with the
private, and presume that we will avoid working groups that include a
requirement for an Object Code License as that too would be a
dealbreaker.
I would not recommend that we proceed with this agreement until we get
these issues resolved.
Also, it is not clear to me what "Exhibit J" refers to.
> 4. The use of the Jakarta EE Compatible trademark is defined in the
> Jakarta EE Trademark Guidelines
> <https://jakarta.ee/legal/trademark_guidelines/>.
>
> [in review?]
Until we decide what we want to do, I'm not sure what there is to
review here. As Mark indicated earlier, it is entirely possible that
we could decide not to make use of the Jakarta EE Compatible mark.
If we do decide we want to use this mark, my reading of this agreement
is that requires either unanimous approval or for us to sign up for
even higher level of membership in the Eclipse Organization.
At the moment, there are too many conditional possibilities involved
to make further recommendations.
> 5. Once the Jakarta EE Trademark Agreement is defined, Eclipse will need
> us to execute that as well, as per the guidelines. This trademark agreement
> is still under development.
>
> [eclipse action item. still in progress]
>
> Items 1, 3 & 4 action items on our side. Do we have ETAs for any of them?
>
> Items 2 & 5 are action items on the Eclipse/Working Group side, 2 is done. I'll get an ETA on 5.
>
> Is there any way I can help with our action items? Being on the WG I can definitely provide answers as well as bring concerns.
I've posted my thoughts publicly, feel free to share them. While my
thoughts alone don't have any particular official status, if the
issues mentioned above can be resolved, getting Brand Management and
Legal Affairs signoff should be easier.
> -David
- Sam Ruby
> > On Jan 18, 2019, at 2:53 PM, Mark Thomas <ma...@apache.org> wrote:
> >
> > Hi all,
> >
> > I am writing to your dev@ lists (on BCC) as your project has, in the
> > past, requested access to the Java EE TCKs while they were controlled by
> > Sun and then Oracle.
> >
> > As I am sure you are aware, Java EE has moved to Eclipse and is now
> > Jakarta EE. The good news is that the TCKs have been open sourced.
> >
> > https://github.com/eclipse-ee4j/jakartaee-tck
> >
> > (I haven't tried to build the latest TCK from source yet but it is on my
> > TODO list.)
> >
> > Shipping compatible implementations of the Jakarta EE specs (and being
> > able to make public statements to that effect) will be subject only to
> > the spec [1] and TCK [2] licenses. There will no longer be a TCK
> > agreement or NDA to sign. However...
> >
> > The question has arisen whether or not any ASF projects will want to use
> > the Jakarta EE compatible logo [3]. If a project wants to be able to do
> > this, there are some organisational hoops to jump through. Before the
> > ASF starts down that path the board has asked me to see if there are any
> > projects that want to use the Jakarta EE compatible logo. After all,
> > there is no point jumping through the hoops if no-one wants to use the logo.
> >
> > With the above in mind can you please discuss this amongst your project
> > community and reply back to jcp-open@apache.org whether or not your
> > project is interested in being able to use the Jakarta EE compatible
> > logo. I ask that you complete this no later than the next board meeting
> > (20th February 2019).
> >
> > If you have any questions about any of the above, please also use
> > jcp-open@apache.org to ask them.
> >
> > Thanks,
> >
> > Mark
> >
> >
> > [1] https://www.eclipse.org/legal/efsl.php
> > [2] https://www.eclipse.org/legal/tck.php
> > [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by David Blevins <da...@gmail.com>.
Following up on some offline threads. High level status of the steps and progress.
1. We join the Eclipse Foundation as a n on-voting Associate Member ($0) -
the Membership Agreement and Membership Application are both here
<https://www.eclipse.org/membership/become_a_member/>
[in review?]
2. A Jakarta EE WG member nominates the ASF as a Guest Member of the working
group. Guest Members must be voted in by the Jakarta EE Steering
Committee, and re-approved annually.
[done]
3. We join the Jakarta EE Working Group as a Guest
Member which will require signing the Working Group
Participation Agreement. The current version of the agreement is
listed under Related Links here
<https://www.eclipse.org/org/workinggroups/about.php> and
requires execution of the main agreement and Exhibit J.
[in review?]
4. The use of the Jakarta EE Compatible trademark is defined in the
Jakarta EE Trademark Guidelines
<https://jakarta.ee/legal/trademark_guidelines/>.
[in review?]
5. Once the Jakarta EE Trademark Agreement is defined, Eclipse will need
us to execute that as well, as per the guidelines. This trademark agreement
is still under development.
[eclipse action item. still in progress]
Items 1, 3 & 4 action items on our side. Do we have ETAs for any of them?
Items 2 & 5 are action items on the Eclipse/Working Group side, 2 is done. I'll get an ETA on 5.
Is there any way I can help with our action items? Being on the WG I can definitely provide answers as well as bring concerns.
-David
> On Jan 18, 2019, at 2:53 PM, Mark Thomas <ma...@apache.org> wrote:
>
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Rémy Maucherat <re...@apache.org>.
On Tue, Feb 12, 2019 at 6:16 PM Mark Thomas <ma...@apache.org> wrote:
> Any other thoughts on this topic?
>
I think we should have EE compatibility back if possible.
Rémy
> Mark
>
>
> On 21/01/2019 10:56, Mark Thomas wrote:
> > Switching hats and speaking as a Tomcat committer.
> >
> > My experience is that folks expect Tomcat to follow the spec and want to
> > know that it does. However, formal certification (or lack of it) hasn't
> > seemed to be a big deal for our users in recent years. I don't know how
> > much of that is because end users care more about actual behaviour than
> > formal certification and how much it is because they understand the
> > historical issues between the ASF and Sun/Oracle over access to the TCKs.
> >
> > Maybe those expectations will change with the specs moving to Eclipse.
> >
> > If the community wants to see the compatibility logo then I have no
> > objection as the requirements don't seem very onerous.
> >
> > Mark
> >
> >
> > On 18/01/2019 22:53, Mark Thomas wrote:
> >> Hi all,
> >>
> >> I am writing to your dev@ lists (on BCC) as your project has, in the
> >> past, requested access to the Java EE TCKs while they were controlled by
> >> Sun and then Oracle.
> >>
> >> As I am sure you are aware, Java EE has moved to Eclipse and is now
> >> Jakarta EE. The good news is that the TCKs have been open sourced.
> >>
> >> https://github.com/eclipse-ee4j/jakartaee-tck
> >>
> >> (I haven't tried to build the latest TCK from source yet but it is on my
> >> TODO list.)
> >>
> >> Shipping compatible implementations of the Jakarta EE specs (and being
> >> able to make public statements to that effect) will be subject only to
> >> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> >> agreement or NDA to sign. However...
> >>
> >> The question has arisen whether or not any ASF projects will want to use
> >> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> >> this, there are some organisational hoops to jump through. Before the
> >> ASF starts down that path the board has asked me to see if there are any
> >> projects that want to use the Jakarta EE compatible logo. After all,
> >> there is no point jumping through the hoops if no-one wants to use the
> logo.
> >>
> >> With the above in mind can you please discuss this amongst your project
> >> community and reply back to jcp-open@apache.org whether or not your
> >> project is interested in being able to use the Jakarta EE compatible
> >> logo. I ask that you complete this no later than the next board meeting
> >> (20th February 2019).
> >>
> >> If you have any questions about any of the above, please also use
> >> jcp-open@apache.org to ask them.
> >>
> >> Thanks,
> >>
> >> Mark
> >>
> >>
> >> [1] https://www.eclipse.org/legal/efsl.php
> >> [2] https://www.eclipse.org/legal/tck.php
> >> [3] https://www.eclipse.org/legal/tck.php
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: dev-help@tomcat.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Any other thoughts on this topic?
Mark
On 21/01/2019 10:56, Mark Thomas wrote:
> Switching hats and speaking as a Tomcat committer.
>
> My experience is that folks expect Tomcat to follow the spec and want to
> know that it does. However, formal certification (or lack of it) hasn't
> seemed to be a big deal for our users in recent years. I don't know how
> much of that is because end users care more about actual behaviour than
> formal certification and how much it is because they understand the
> historical issues between the ASF and Sun/Oracle over access to the TCKs.
>
> Maybe those expectations will change with the specs moving to Eclipse.
>
> If the community wants to see the compatibility logo then I have no
> objection as the requirements don't seem very onerous.
>
> Mark
>
>
> On 18/01/2019 22:53, Mark Thomas wrote:
>> Hi all,
>>
>> I am writing to your dev@ lists (on BCC) as your project has, in the
>> past, requested access to the Java EE TCKs while they were controlled by
>> Sun and then Oracle.
>>
>> As I am sure you are aware, Java EE has moved to Eclipse and is now
>> Jakarta EE. The good news is that the TCKs have been open sourced.
>>
>> https://github.com/eclipse-ee4j/jakartaee-tck
>>
>> (I haven't tried to build the latest TCK from source yet but it is on my
>> TODO list.)
>>
>> Shipping compatible implementations of the Jakarta EE specs (and being
>> able to make public statements to that effect) will be subject only to
>> the spec [1] and TCK [2] licenses. There will no longer be a TCK
>> agreement or NDA to sign. However...
>>
>> The question has arisen whether or not any ASF projects will want to use
>> the Jakarta EE compatible logo [3]. If a project wants to be able to do
>> this, there are some organisational hoops to jump through. Before the
>> ASF starts down that path the board has asked me to see if there are any
>> projects that want to use the Jakarta EE compatible logo. After all,
>> there is no point jumping through the hoops if no-one wants to use the logo.
>>
>> With the above in mind can you please discuss this amongst your project
>> community and reply back to jcp-open@apache.org whether or not your
>> project is interested in being able to use the Jakarta EE compatible
>> logo. I ask that you complete this no later than the next board meeting
>> (20th February 2019).
>>
>> If you have any questions about any of the above, please also use
>> jcp-open@apache.org to ask them.
>>
>> Thanks,
>>
>> Mark
>>
>>
>> [1] https://www.eclipse.org/legal/efsl.php
>> [2] https://www.eclipse.org/legal/tck.php
>> [3] https://www.eclipse.org/legal/tck.php
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Switching hats and speaking as a Tomcat committer.
My experience is that folks expect Tomcat to follow the spec and want to
know that it does. However, formal certification (or lack of it) hasn't
seemed to be a big deal for our users in recent years. I don't know how
much of that is because end users care more about actual behaviour than
formal certification and how much it is because they understand the
historical issues between the ASF and Sun/Oracle over access to the TCKs.
Maybe those expectations will change with the specs moving to Eclipse.
If the community wants to see the compatibility logo then I have no
objection as the requirements don't seem very onerous.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Jakarta EE TCKs and compatibility logo
Posted by Richard Monson-Haefel <mo...@gmail.com>.
+1
On Fri, Jan 18, 2019 at 4:53 PM Mark Thomas <ma...@apache.org> wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the
> logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
--
Richard Monson-Haefel
https://twitter.com/rmonson
https://www.linkedin.com/in/monsonhaefel/
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by César Hernández Mendoza <ce...@gmail.com>.
+1 on having the Jakarta TCK Compatibility Logo for ASF projects.
Currently, GitHub readme already provides some batches:
[image: image.png]
El sáb., 19 ene. 2019 a las 1:38, Romain Manni-Bucau (<rm...@gmail.com>)
escribió:
> Hello guys,
>
> What's your opinion on this?
> Personally I think we don't care while spec+tck are OS.
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> | Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
>
>
> ---------- Forwarded message ---------
> From: Mark Thomas <ma...@apache.org>
> Date: ven. 18 janv. 2019 à 23:53
> Subject: Jakarta EE TCKs and compatibility logo
> To: <jc...@apache.org>
>
>
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the
> logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
--
Atentamente:
César Hernández Mendoza.
Fwd: Jakarta EE TCKs and compatibility logo
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hello guys,
What's your opinion on this?
Personally I think we don't care while spec+tck are OS.
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>
---------- Forwarded message ---------
From: Mark Thomas <ma...@apache.org>
Date: ven. 18 janv. 2019 à 23:53
Subject: Jakarta EE TCKs and compatibility logo
To: <jc...@apache.org>
Hi all,
I am writing to your dev@ lists (on BCC) as your project has, in the
past, requested access to the Java EE TCKs while they were controlled by
Sun and then Oracle.
As I am sure you are aware, Java EE has moved to Eclipse and is now
Jakarta EE. The good news is that the TCKs have been open sourced.
https://github.com/eclipse-ee4j/jakartaee-tck
(I haven't tried to build the latest TCK from source yet but it is on my
TODO list.)
Shipping compatible implementations of the Jakarta EE specs (and being
able to make public statements to that effect) will be subject only to
the spec [1] and TCK [2] licenses. There will no longer be a TCK
agreement or NDA to sign. However...
The question has arisen whether or not any ASF projects will want to use
the Jakarta EE compatible logo [3]. If a project wants to be able to do
this, there are some organisational hoops to jump through. Before the
ASF starts down that path the board has asked me to see if there are any
projects that want to use the Jakarta EE compatible logo. After all,
there is no point jumping through the hoops if no-one wants to use the logo.
With the above in mind can you please discuss this amongst your project
community and reply back to jcp-open@apache.org whether or not your
project is interested in being able to use the Jakarta EE compatible
logo. I ask that you complete this no later than the next board meeting
(20th February 2019).
If you have any questions about any of the above, please also use
jcp-open@apache.org to ask them.
Thanks,
Mark
[1] https://www.eclipse.org/legal/efsl.php
[2] https://www.eclipse.org/legal/tck.php
[3] https://www.eclipse.org/legal/tck.php
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Mark Thomas <ma...@apache.org>.
Apologies for the noise.
The correct link for [3] is:
https://jakarta.ee/legal/trademark_guidelines/
I've also corrected a handful of the project BCCs.
Mark
On 18/01/2019 22:53, Mark Thomas wrote:
> Hi all,
>
> I am writing to your dev@ lists (on BCC) as your project has, in the
> past, requested access to the Java EE TCKs while they were controlled by
> Sun and then Oracle.
>
> As I am sure you are aware, Java EE has moved to Eclipse and is now
> Jakarta EE. The good news is that the TCKs have been open sourced.
>
> https://github.com/eclipse-ee4j/jakartaee-tck
>
> (I haven't tried to build the latest TCK from source yet but it is on my
> TODO list.)
>
> Shipping compatible implementations of the Jakarta EE specs (and being
> able to make public statements to that effect) will be subject only to
> the spec [1] and TCK [2] licenses. There will no longer be a TCK
> agreement or NDA to sign. However...
>
> The question has arisen whether or not any ASF projects will want to use
> the Jakarta EE compatible logo [3]. If a project wants to be able to do
> this, there are some organisational hoops to jump through. Before the
> ASF starts down that path the board has asked me to see if there are any
> projects that want to use the Jakarta EE compatible logo. After all,
> there is no point jumping through the hoops if no-one wants to use the logo.
>
> With the above in mind can you please discuss this amongst your project
> community and reply back to jcp-open@apache.org whether or not your
> project is interested in being able to use the Jakarta EE compatible
> logo. I ask that you complete this no later than the next board meeting
> (20th February 2019).
>
> If you have any questions about any of the above, please also use
> jcp-open@apache.org to ask them.
>
> Thanks,
>
> Mark
>
>
> [1] https://www.eclipse.org/legal/efsl.php
> [2] https://www.eclipse.org/legal/tck.php
> [3] https://www.eclipse.org/legal/tck.php
>
Re: Jakarta EE TCKs and compatibility logo
Posted by Daniel Cunha <da...@apache.org>.
+1
Em seg, 21 de jan de 2019 às 13:44, César Hernández Mendoza <
cesarguate@gmail.com> escreveu:
> +1
>
> El dom., 20 ene. 2019 a las 7:03, Frankie (<ka...@gmx.de>)
> escribió:
>
> > +1
> >
> > Frankie
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >
>
>
> --
> Atentamente:
> César Hernández Mendoza.
>
--
Daniel "soro" Cunha
https://twitter.com/dvlc_
Re: Jakarta EE TCKs and compatibility logo
Posted by César Hernández Mendoza <ce...@gmail.com>.
+1
El dom., 20 ene. 2019 a las 7:03, Frankie (<ka...@gmx.de>)
escribió:
> +1
>
> Frankie
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
--
Atentamente:
César Hernández Mendoza.
Re: Jakarta EE TCKs and compatibility logo
Posted by Frankie <ka...@gmx.de>.
+1
Frankie
--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html