[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
Re: [jakartaee-platform-dev] [External] : Re: [jakarta.ee-steering] Quick update on Jakarta EE 10 release
 | 
  
    It seems that the DI 2.0.2 TCK is /already/ pushed to the
      Specification Download page. The only thing amiss is that the
      Spec. page itself isn't updated. I will start a PR (524)
      to handle that. The same seems to be true for Bean Validation 3. A
      newer service release that isn't reflected on its Spec. page is
      already pushed to the Specifications Downloads. So, I've added
      that to PR 524.
    Lastly, it look like the BV SHA Sum on the TCK Results Page is
      incorrect. I believe the correct SHA-256 sum should be:
      9da36d2d6e2eb8d413f886f15711820008419d210ce4c51af04f96e1ffd583b3
    If you look at both the CCR and the TCK Results page, you'll
      notice the sums for BV on both pages appear to be short. 
    
    Arjan, could you update the CCR and TCK Results page?
    Thanks,
    -- Ed
    
    On 7/12/2022 4:17 PM, Ed Bratt wrote:
    
    
      
      Per the meeting this morning (Agenda):
      Faces Spec. bug-fix is in progress. See Specifications PR
          521
      Problems with RESTFul Web Services Spec. page are fixed. PR
          522
      Authentication and Activation issues still need resolution.
      I neglected to remind us in the meeting, we also need to update
        the latest service releases of DI 2.0 (2.0.2) and Bean
        Validation (2.0.1).  If representatives of those committer
        groups could confirm that these TCKs are ready to be published,
        we can push them to the Spec. download area and update the
        Specification pages.
      
      
      
      On 7/12/2022 8:53 AM, Ed Bratt wrote:
      
      
        I will be happy to push this final version from the staged
          location to the Specifications Download area. But first, do
          you want the staged file to end in .zip.zip? (https://download.eclipse.org/ee4j/jakartaee-tck/jakartaee10/staged/eftl/jakarta-faces-tck-4.0.1.zip.zip)
        Once you confirm and/or update the staged file-name, I'll do
          the push.
        Thanks,
        -- Ed
        
        On 7/12/2022 4:31 AM, arjan tijms
          wrote:
        
        
          Just as I hit send, the job executed. The Faces
            4.0.1 TCK is now here:
            
            
            
           
          
          
            
            
              Hi,
                
                
                
                
                
                
                
                
                
                
                
                Kind regards,
                Arjan Tijms
                
                
                
                
                
                
               
              
              
                
                
                  
                    
                      
                      
                        
                        
                          
                            This is great news.
                            Moving this to the Platform Dev list -- I
                              looked at some of the TCK details --
                            
                            I think we need the following updates to
                              happen:
                            
                              - Dependency Injection: Update
                                specification page to add the 2.0.2
                                release/TCK
 
                              - Bean Validation: Update specification
                                page to add the 2.0.1 release/TCK
 
                            
                            The following TCK SHA sums don't match
                              what's published at Jakarta EE
                              Specification page
                            
                              - Activation 2.1 -- I'm not sure what
                                happened to this TCK. If it has been
                                rebuilt and the current staged TCK must
                                be used, a 2.1.1 bug-fix should be
                                pushed.
 
                              
                              - Faces 4.0 -- I'm not sure what
                                happened to this TCK. If it has been
                                rebuilt and the current staged TCK must
                                be used, a 4.0.1 bug-fix should be
                                pushed.
 
                              
                              - Authentication 3.0 -- There is a PR open in
                                the Spec. repo and it appears to point
                                to a TCK with the correct SHA sum.
                                Shouldn't this be called a bug-fix
                                release (i.e. 3.0.1)? This is related to
                                the merging of all TCK tests into a
                                single PR (previously, it was in two
                                separate TCKs). This PR should be merged
                                when it's ready.
                               
                            
                           
                        
                       
                     
                    We are just now starting to try
                      running the old platform TCK produced auth TCK
                      which needs a new ts.jte to be filled in (using
                      jaspic.home instead of javaee.home since we aren't
                      running this as part of the Platform TCK).  
                    
                    
                    We missed our chance to correct the
                      old auth TCK user guide doc, it refers to 2.0
                      instead of 3.0.  Can we fix the old auth TCK ug by
                      building and staging a 3.0.1 from the
                      authentication project?  I'm not sure that we need
                      to but wanted to mention it as a possible option
                      (if the authentication project is prepared to do
                      this work now).
                    
                    
                    Scott
                    
                   
                
               
            
           
          
          
          _______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!PO1U9Dys3AFQdKJ27SP0fwRVO6qL7gwtg5YKfvtKKmLAZkbmL6x-Dh8d56-GQ8N1n5xpodi3aA692ljB_jk$ 
        
        
        
        _______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!OJ2c-8fjmtLKbs3W7l-dqLG8Z6QLgi6uDng5GKEmUWjtOuYOJEQ08gNHbNdtIlJqvjssxsroHVao48uB$ 
      
      
      
      _______________________________________________
jakartaee-platform-dev mailing list
jakartaee-platform-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://urldefense.com/v3/__https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev__;!!ACWV5N9M2RV99hQ!I26_vZPY7SlnbBdSvRQg8iOyakqhU7VlwtdCSB3xxuX4wIEwLXIKA_BgSsfU6hAwfwsQn9S6Kmc6eZuR$