-
Notifications
You must be signed in to change notification settings - Fork 491
Closed
Description
I believe that the API change of the fourth argument boolean (primitive type, nulls not allowed) to Boolean (object, nulls allowed) is a breaking change in pull request:
The change in the diff went from this:
public ProjectHook addHook(Object projectIdOrPath, String url, ProjectHook enabledHooks,
boolean enableSslVerification, String secretToken) throws GitLabApiException {
to this:
public ProjectHook addHook(Object projectIdOrPath, String url, ProjectHook enabledHooks,
Boolean enableSslVerification, String secretToken) throws GitLabApiException {
The Jenkins issue tracker received two reports of method not found exceptions in issue JENKINS-73672.
Is there a critical need for the change of type in the argument?
If not, could that change be reverted and a new release provided so that API compatibility is retained?
Metadata
Metadata
Assignees
Labels
No labels