[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [jakartaee-platform-dev] Understanding a few javax->jakarta decisions | 
  
  
    Kevin will tell me if I got this wrong, but...  Here's what I
    remember...
    
    
Scott Kurz wrote on 3/6/20 1:40 PM:
    
    
      
      Late to the discussion, I wanted to see where
          we'd settled on the EE 9 plan questions (I see some discussion
          on the various lists)
        
        1. Whether it is OK to add generic support in EE
          9 along with the package move
      
    
    It's ok, but you'll need to file your own release
      plan since you're stepping outside what the platform release plan
      says.
      
    
    
      2. Whether spec-defined properties should move
          from javax. to jakarta.* (along w/ packages)
      
    
    Yes, definitely.
      
    
    
      3. Whether the targetNamespace for the Batch XML
          / XSD needs to change (currently
          using   targetNamespace="http://xmlns.jcp.org/xml/ns/javaee%22)
      
    
    Yes, definitely.  I don't think we've decided on the
      new base namespace yet; we're waiting for advice from Eclipse.
      
    
    
      
        But I don't see any of this here:  https://eclipse-ee4j.github.io/jakartaee-platform/jakartaee9/JakartaEE9ReleasePlan  
        
      
    
    Seems like we need to start a FAQ!
      
    
    
      
        Now... if these three items are still under
          discussion then I can dig through the various threads... I'm
          not asking anyone to go collect links for me. 
        
        But I'm just asking in case maybe there already
          is a consensus captured somewhere and I'm just not looking in
          the right place... and/or maybe that "release plan" doc just
          needs to be updated?
        
          If that's the doc that needs to be updated can someone please
          point me to the repo to open the issue on?
      
    
    My answers above are from memory, so they might not be perfect. 
    Filing these as issues in the platform project is one way to record
    the decisions, but I think people would find it easier to find the
    answers to their questions if we started a FAQ.