[JBPM-4951] JBPM Rest API to Create Repository doesnt seem to work#914
[JBPM-4951] JBPM Rest API to Create Repository doesnt seem to work#914rnetuka wants to merge 1 commit intoAppFormer:masterfrom
Conversation
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
1 similar comment
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
|
ok to test |
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
2 similar comments
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
|
@mswiderski Can you please advise what is considered appropriate for REST changes? Do you know if this is covered by REVAPI plugin? |
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
2 similar comments
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
|
Jenkins please execute full downstream build. |
|
@manstis I don't think this need any revapi setup as it does not change the api. if needed, it should be documented only that there are erroneous condition and appropriate http status codes are returned to provide meaningful response. |
|
Can one of the admins verify this PR? Comment with 'ok to test' to start the build. |
manstis
left a comment
There was a problem hiding this comment.
Awaiting PR for new/updated unit tests on kie-wb-distributions
|
Can you please move this PR for https://github.com/kiegroup/appformer ? |
JIRA: https://issues.jboss.org/browse/JBPM-4951
Missing organizationalUnitName property now returns 400 Bad Request (with explanation) rather than 404 Not Found.
Invalid organizational unit now returns correct Content-Type: text/plain