[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| Re: [ee4j-pmc] [jakartaee-spec-project-leads] Preparing for Jakarta EE 8 Release | 
Well, I left it in there because, in my opinion, it leaves historical evidence of what was done. It's not confusing at all. In fact, its far clearer than having no version.  That said, I'm no married to having it in there. If folks want it removed and there is consensus than I'll remove all the @versions entirely for change them back to JMS 2.0 or whatever.
  
    
  
  
    There's a separate discussion going on on the spec committee private
    list about that.  We haven't reached a conclusion yet but at least
    two of us are leaning towards removing it.  If you think it's
    important to keep @version, explain why.
    
    Richard Monson-Haefel wrote on 7/18/19
      2:45 PM:
    
    
      
      Right. The since is whatever it was to begin with.
        The version is the JMS version (e.g. 2.1) but with Jakarta
        Messaging.  
        
        
        But then you said  "Remove @version!  :-)" .  Which I can't
          tell if its humor or serious; advice or recommendation.
      
      
        
        
           For an API added in 2.1, yes.
            
            For an API added in 2.0 it would be:
            
            
@version Jakarta Messaging 2.1
            
            @since JMS 2.0
            
            Does that seem weird?  Remove @version!  :-)
            
            
Richard
              Monson-Haefel wrote on 7/18/19 2:11 PM:
            
            
              Does that mean files would look as follows:
                
                
                
                
                @version Jakarta Messaging 2.1
                
                @since JMS 2.1
                
                
                
                
                
                Like that?
                
                
              
              
                
                
                   That's my understanding of its
                    intent.  If it's not updated when a new version of
                    the API is released, it just becomes another form of
                    @since.
                    
                    Scott
                      Stark wrote on 7/18/19 1:00 PM:
                    
                     Can’t this just be
                      generated then? Your saying this needs to match
                      the pom.xml version?
                      
                        
                          
                          
                          
                             @version is supposed
                              to be the current version of the API, so
                              it needs to be updated for each release,
                              and thus should have the new API name. 
                              (If you don't update it, it degenerates to
                              being the same as @since.)
                              
                              Richard
                                Monson-Haefel wrote on 7/18/19 8:45 AM:
                              
                              
                                Hi Scott,
                                  
                                  
                                  this line tripped me up "
                                  
                                    - Leave
                                      existing "@since XYZ 1.x" uses
                                      alone. These refer to the old JCP
                                      version. Future additions should
                                      use the Jakarta project name.
                                  Can you add another line about leaving
                                  the @version the same as well?  That's
                                  where I went wrong.
                             
                        
                       
                      
                      
                      
                      _______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
                    
                    
                  
                  ee4j-pmc mailing list
                  ee4j-pmc@xxxxxxxxxxx
                  To change your delivery options, retrieve your
                  password, or unsubscribe from this list, visit
                  https://www.eclipse.org/mailman/listinfo/ee4j-pmc
                
               
              
              
              
              -- 
              
              
              
              _______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
            
            
          
       
      
      
      
      -- 
      
    
    
  
--