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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Yesterday’s PR was flawed, my mistake. While testing the integration this morning, I realised I had added the apiKey in the body instead of as a request parameter. This update should fix the issue.
PS: I’ve been trying to package it locally to test directly with my code, but after an hour I keep running into issues with the licence plugin failing to execute. Any chance you could run it quickly on your side, or share the instructions to get it working? Sorry about that, it feels a bit amateurish, but I need to move on to other tasks today. I’m fairly confident the mistake from last time is fixed after re-reading the documentation, but I would have preferred to test it properly.
Yesterday’s PR was flawed, my mistake. While testing the integration this morning, I realised I had added the apiKey in the body instead of as a request parameter. This update should fix the issue.
PS: I’ve been trying to package it locally to test directly with my code, but after an hour I keep running into issues with the licence plugin failing to execute. Any chance you could run it quickly on your side, or share the instructions to get it working? Sorry about that, it feels a bit amateurish, but I need to move on to other tasks today. I’m fairly confident the mistake from last time is fixed after re-reading the documentation, but I would have preferred to test it properly.
You can just comment out the license plugin in the pom.xml and it will run. But none the less, I tested this and was able to get passed verification.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yesterday’s PR was flawed, my mistake. While testing the integration this morning, I realised I had added the apiKey in the body instead of as a request parameter. This update should fix the issue.
PS: I’ve been trying to package it locally to test directly with my code, but after an hour I keep running into issues with the licence plugin failing to execute. Any chance you could run it quickly on your side, or share the instructions to get it working? Sorry about that, it feels a bit amateurish, but I need to move on to other tasks today. I’m fairly confident the mistake from last time is fixed after re-reading the documentation, but I would have preferred to test it properly.