siom79
commented
5 years ago No, japicmp does not distinguish between provider and consumer.
Am Do., 11. Apr. 2019, 10:24 hat elballa notifications@github.com geschrieben:
Hi, has japicmp plugin a way to distinguish between interfaces designed for providers (like javax.servlet.ServletContext) and those designed for consumers (like javax.servlet.Servlet) as bnd-baseline does? Provider is a person implementing an API and a Consumer is a person using the API. Marking interface for a specific "person" can change the severty of the source code changes in terms of backward compatibility. In the examples of the Servlet API, adding a method to the ServletContext would be a minor change because it only requires an update to the providers (like Tomcat or Jetty) and has no any impact to the consumers. Adding a method to the Servlet interface, however, would break all WAR files and therefore be a major change. Thanks
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/siom79/japicmp/issues/234, or mute the thread https://github.com/notifications/unsubscribe-auth/ADlPtMWUNZnv31-pdV--jSAzjQbesUeAks5vfvFQgaJpZM4cpBh7 .
elballa
Hi, has japicmp plugin a way to distinguish between interfaces designed for providers (like javax.servlet.ServletContext) and those designed for consumers (like javax.servlet.Servlet) as bnd-baseline does? Provider is a person implementing an API and a Consumer is a person using the API. Marking interface for a specific "person" can change the severty of the source code changes in terms of backward compatibility. In the examples of the Servlet API, adding a method to the ServletContext would be a minor change because it only requires an update to the providers (like Tomcat or Jetty) and has no any impact to the consumers. Adding a method to the Servlet interface, however, would break all WAR files and therefore be a major change. Thanks