You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@xerces.apache.org by Mark Thomas <ma...@apache.org> on 2019/01/21 10:46:37 UTC
Re: Jakarta EE TCKs and compatibility logo
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 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 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 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 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
>>
>
---------------------------------------------------------------------
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
>>
>
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@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 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
>>
>