Re: Potential release vote for 8.0.7 and 9.0.0-M7

2021-04-30 Thread Gurkan Erdogdu
Skip my previous question.
Regards.
Gurkan

On Sat, May 1, 2021 at 8:57 AM Gurkan Erdogdu  wrote:

> AFAIK, (please correct me if I am wrong), ASF is not a member of the
> Jakarta EE working group and is not able to get certified. How will TomEE
> get certified?
> Because of this, Tomcat is not able to be listed in certification pages of
> Servlet specification.
>
> Regards.
> Gurkan
>
> On Sat, May 1, 2021 at 4:32 AM David Blevins 
> wrote:
>
>> Heads up that we are narrowing in in the last few TCK issues and there is
>> still some chance we can be Jakarta EE 9.1 Web Profile certified in time
>> for the Jakarta EE 9.1 release vote Monday.
>>
>> It would be super super and I mean *super* tight
>>
>> However, if we can get it done we'll need to do a release vote by no
>> later than Sunday afternoon and file our certification request.  We don't
>> need to have concluded our vote to make the Jakarta EE 9.1 release ballot,
>> we just need final binaries of our own to be at least in staging and in the
>> process of our own vote.
>>
>> We do need that vote pass, however, so that would require some pragmatism
>> on all our parts.
>>
>> For that reason I recommend we do not try to push out a 9.0.0 final, but
>> go ahead with 9.0.0-M7. If there are some issues with the binaries we put
>> up for vote, unless they are legal issues, we can still release them and
>> immediately fix the issues next week in a subsequent 8.0.8 and 9.0.0-M8.
>> There's no reason to "wait", we can simply release twice.  Version numbers
>> are free.
>>
>> The Jakarta EE 9.1 release vote lasts for two weeks and an announcement
>> would happen some days after that.  Ff we did want to push out a 9.0.0 for
>> the announcement, we'd have at least till May 17th to do that, perhaps even
>> the 20th.
>>
>> The reason we want to get certified in time for the ballot is recently
>> there was a change that implementations listed on the ballot get a special
>> place at the top of the specification page.  Any implementations that come
>> even one day later cannot be included and will not be accepted or given
>> special designation.  This lasts forever and is a permanent advantage to
>> those in the list.  It's also a permanent *disadvantage* to those not on
>> the list.  It's eat or be eaten.
>>
>> So that's what we're going for:  A staged binary up for a vote here,
>> passing the TCK, in time to be listed on the Jakarta EE 9.1 release ballot
>> Monday.
>>
>>
>> -David
>>
>>


Re: Potential release vote for 8.0.7 and 9.0.0-M7

2021-04-30 Thread Gurkan Erdogdu
AFAIK, (please correct me if I am wrong), ASF is not a member of the
Jakarta EE working group and is not able to get certified. How will TomEE
get certified?
Because of this, Tomcat is not able to be listed in certification pages of
Servlet specification.

Regards.
Gurkan

On Sat, May 1, 2021 at 4:32 AM David Blevins 
wrote:

> Heads up that we are narrowing in in the last few TCK issues and there is
> still some chance we can be Jakarta EE 9.1 Web Profile certified in time
> for the Jakarta EE 9.1 release vote Monday.
>
> It would be super super and I mean *super* tight
>
> However, if we can get it done we'll need to do a release vote by no later
> than Sunday afternoon and file our certification request.  We don't need to
> have concluded our vote to make the Jakarta EE 9.1 release ballot, we just
> need final binaries of our own to be at least in staging and in the process
> of our own vote.
>
> We do need that vote pass, however, so that would require some pragmatism
> on all our parts.
>
> For that reason I recommend we do not try to push out a 9.0.0 final, but
> go ahead with 9.0.0-M7. If there are some issues with the binaries we put
> up for vote, unless they are legal issues, we can still release them and
> immediately fix the issues next week in a subsequent 8.0.8 and 9.0.0-M8.
> There's no reason to "wait", we can simply release twice.  Version numbers
> are free.
>
> The Jakarta EE 9.1 release vote lasts for two weeks and an announcement
> would happen some days after that.  Ff we did want to push out a 9.0.0 for
> the announcement, we'd have at least till May 17th to do that, perhaps even
> the 20th.
>
> The reason we want to get certified in time for the ballot is recently
> there was a change that implementations listed on the ballot get a special
> place at the top of the specification page.  Any implementations that come
> even one day later cannot be included and will not be accepted or given
> special designation.  This lasts forever and is a permanent advantage to
> those in the list.  It's also a permanent *disadvantage* to those not on
> the list.  It's eat or be eaten.
>
> So that's what we're going for:  A staged binary up for a vote here,
> passing the TCK, in time to be listed on the Jakarta EE 9.1 release ballot
> Monday.
>
>
> -David
>
>


Potential release vote for 8.0.7 and 9.0.0-M7

2021-04-30 Thread David Blevins
Heads up that we are narrowing in in the last few TCK issues and there is still 
some chance we can be Jakarta EE 9.1 Web Profile certified in time for the 
Jakarta EE 9.1 release vote Monday.

It would be super super and I mean *super* tight

However, if we can get it done we'll need to do a release vote by no later than 
Sunday afternoon and file our certification request.  We don't need to have 
concluded our vote to make the Jakarta EE 9.1 release ballot, we just need 
final binaries of our own to be at least in staging and in the process of our 
own vote.

We do need that vote pass, however, so that would require some pragmatism on 
all our parts.

For that reason I recommend we do not try to push out a 9.0.0 final, but go 
ahead with 9.0.0-M7. If there are some issues with the binaries we put up for 
vote, unless they are legal issues, we can still release them and immediately 
fix the issues next week in a subsequent 8.0.8 and 9.0.0-M8.  There's no reason 
to "wait", we can simply release twice.  Version numbers are free.

The Jakarta EE 9.1 release vote lasts for two weeks and an announcement would 
happen some days after that.  Ff we did want to push out a 9.0.0 for the 
announcement, we'd have at least till May 17th to do that, perhaps even the 
20th.

The reason we want to get certified in time for the ballot is recently there 
was a change that implementations listed on the ballot get a special place at 
the top of the specification page.  Any implementations that come even one day 
later cannot be included and will not be accepted or given special designation. 
 This lasts forever and is a permanent advantage to those in the list.  It's 
also a permanent *disadvantage* to those not on the list.  It's eat or be eaten.

So that's what we're going for:  A staged binary up for a vote here, passing 
the TCK, in time to be listed on the Jakarta EE 9.1 release ballot Monday.


-David



smime.p7s
Description: S/MIME cryptographic signature


[GitHub] [tomee-site-generator] cesarhernandezgt commented on a change in pull request #22: TOMEE-3733 Jakarta EE TCK summary page

2021-04-30 Thread GitBox


cesarhernandezgt commented on a change in pull request #22:
URL: 
https://github.com/apache/tomee-site-generator/pull/22#discussion_r624007146



##
File path: pom.xml
##
@@ -121,7 +121,7 @@
 
   org.apache.tika
   tika-parsers
-  1.25
+  1.17

Review comment:
   Hi Richard, thanks for the review. 
   Yes, I sent the why on the email, maybe I should added here too :P
   
   I marked the PR as draft since a couple of Jakarta EE links needs to be 
updated along with dates and  sha's




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [tomee-site-generator] rzo1 commented on a change in pull request #22: TOMEE-3733 Jakarta EE TCK summary page

2021-04-30 Thread GitBox


rzo1 commented on a change in pull request #22:
URL: 
https://github.com/apache/tomee-site-generator/pull/22#discussion_r623996220



##
File path: pom.xml
##
@@ -121,7 +121,7 @@
 
   org.apache.tika
   tika-parsers
-  1.25
+  1.17

Review comment:
   ~~Any reason for the downgrade? :)~~
   
   Mailing list thread explains it :)




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




TOMEE-3733 - Results page for website

2021-04-30 Thread Cesar Hernandez
Hi,

I started to work on the website to add a new page to display the Jakarta
EE TCK summary results base
on the  information required by Eclipse Foundation Technology Compatibility
Kit License [1]
I just created  https://issues.apache.org/jira/browse/TOMEE-3733 and PR is
also available with the first
iteration: https://github.com/apache/tomee-site-generator/pull/22

As a side note, at the beginning I struggle a bit trying to run locally the
project
https://github.com/apache/tomee-site-generator/ because when I tried to run
 mvn compile -Djbake.http=true
the server failed to start with java.lang.IllegalArgumentException
at org.apache.xbean.asm5.ClassReader exception [2]

To fix this I had to downgrade the tika-parsers from 1.25 to 1.17 because
according
to 1.17 release note [3] the project dropped support for Java 7 around that
version.
I made sure that download-ng.java worked fine before and after the change
so no regressions were
introduced by downgrading the tika-parsers since the jar is only used when
running
org.apache.tomee.website.DownloadsNG.java standalone runner.


[1]
https://www.eclipse.org/legal/tck.php

[2]
java.lang.IllegalArgumentException: java.lang.IllegalArgumentException
at org.apache.tomee.embedded.Container.deploy(Container.java:272)
at
org.apache.tomee.embedded.Container.deployPathsAsWebapp(Container.java:228)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:193)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:173)
at
org.apache.tomee.embedded.Container.deployClasspathAsWebApp(Container.java:164)
at org.apache.tomee.website.JBake.main(JBake.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at org.apache.xbean.asm5.ClassReader.(Unknown Source)
at
org.apache.xbean.finder.AnnotationFinder.readClassDef(AnnotationFinder.java:1169)
at
org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:147)
at
org.apache.xbean.finder.AnnotationFinder.(AnnotationFinder.java:160)
at
org.apache.openejb.config.FinderFactory$OpenEJBAnnotationFinder.(FinderFactory.java:546)
at org.apache.tomee.embedded.Container.deploy(Container.java:268)

[3]
https://archive.apache.org/dist/tika/CHANGES-1.17.txt
-- 
Atentamente:
César Hernández.


[GitHub] [tomee] rzo1 merged pull request #788: TOMEE-3732 - MyFaces 2.3.9

2021-04-30 Thread GitBox


rzo1 merged pull request #788:
URL: https://github.com/apache/tomee/pull/788


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [tomee-site-generator] rzo1 commented on a change in pull request #22: TOMEE-3733 Jakarta EE TCK summary page

2021-04-30 Thread GitBox


rzo1 commented on a change in pull request #22:
URL: 
https://github.com/apache/tomee-site-generator/pull/22#discussion_r623996220



##
File path: pom.xml
##
@@ -121,7 +121,7 @@
 
   org.apache.tika
   tika-parsers
-  1.25
+  1.17

Review comment:
   Any reason for the downgrade? :)




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org




[GitHub] [tomee-site-generator] cesarhernandezgt commented on pull request #22: TOMEE-3733 Jakarta EE TCK summary page

2021-04-30 Thread GitBox


cesarhernandezgt commented on pull request #22:
URL: 
https://github.com/apache/tomee-site-generator/pull/22#issuecomment-830199188


   Small section added in the download page:
   
![image](https://user-images.githubusercontent.com/1454523/116722024-2a526500-a99b-11eb-9f7c-70934593e80f.png)
   
   New TCK summary page:
   
![image](https://user-images.githubusercontent.com/1454523/116722521-b82e5000-a99b-11eb-836a-0c91d1136d38.png)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org