[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openejb-development
Subject:    [GitHub] [tomee] emecas commented on issue #626: TOMEE-2759-Update-Eclipse-Krazo
From:       GitBox <git () apache ! org>
Date:       2020-02-25 22:06:02
Message-ID: 158266836239.8951.1451424577720641912.gitbox () gitbox ! apache ! org
[Download RAW message or body]

emecas commented on issue #626: TOMEE-2759-Update-Eclipse-Krazo
URL: https://github.com/apache/tomee/pull/626#issuecomment-591094503
 
 
   This could be a little off-topic [or not :)] 
   
   Since this upgrade only applied for those 3 examples, is there a way to include a \
check to validate the tests for each example are still passing , or is something like \
that already on place? or even covered and implicit to the general build?  
   Should not be the process for upgrading dependencies a more rigorous process ? at \
least from the point of view of documenting,  or letting know what is the specific \
benefit of doing it, or why it is important, or by the simple fact of checking and \
ensure full backward compatibility.  
   Also it could be part of the description of the Dependency upgrade JIRA issue?
   
   By the way there is already a new release after the one included in this PR.
   https://github.com/eclipse-ee4j/krazo/releases/tag/1.1.0-M1
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services


[prev in list] [next in list] [prev in thread] [next in thread]