You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have using your wonderful tool to detect the breaking compatibility changes in my framework.
By pattern, my framework happens to have the same classes (for different implementations) in different jars.
Ex: LoggerSpring4 and LoggerSpring5. Both with the same package and name but in different jars (one for spring 4 and one for spring5).
I ran your product and the results seem to be a little weird (even if it does not make it crash). I assume you did not take into account that use case.
Could you confirm my assumption ? And if yes, would it be possible to fix that ? Basically handle this usecase.
The text was updated successfully, but these errors were encountered:
I have using your wonderful tool to detect the breaking compatibility changes in my framework.
By pattern, my framework happens to have the same classes (for different implementations) in different jars.
Ex: LoggerSpring4 and LoggerSpring5. Both with the same package and name but in different jars (one for spring 4 and one for spring5).
I ran your product and the results seem to be a little weird (even if it does not make it crash). I assume you did not take into account that use case.
Could you confirm my assumption ? And if yes, would it be possible to fix that ? Basically handle this usecase.
The text was updated successfully, but these errors were encountered: