-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use proper gradle dep. to fetch security plugin #566
use proper gradle dep. to fetch security plugin #566
Conversation
CC @dblock @ankitkala @prudhvigodithi (you were involved in the original maven discussions) |
Codecov Report
@@ Coverage Diff @@
## main #566 +/- ##
============================================
- Coverage 75.10% 73.31% -1.79%
+ Complexity 1008 987 -21
============================================
Files 141 141
Lines 4595 4595
Branches 506 506
============================================
- Hits 3451 3369 -82
- Misses 832 913 +81
- Partials 312 313 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
just realised that in my local test i failed to pass the problem is that so far you had an i've now reduced my change to only change the gradle behaviour and leave the whole |
there's no need to manually construct a URL and try to fetch the artefact from there. the plugin is published on maven and we can directly use the gradle/maven dependency to fetch it. in order to more easily identify it, a new configuration type has been added: `opensearchPlugin`. for reference see the discussions on the following issues/PRs: - #274 - #455 Signed-off-by: Ralph Ursprung <Ralph.Ursprung@avaloq.com>
i think the current set of build failures is unrelated, i also get them on a clean |
Yep. Those are unrelated. I've triggered a retry. Thanks for fixing this btw :-) |
i've now raised opensearch-project/OpenSearch#4589 |
@rursprung Should we use the same approach for things like opensearch-project/job-scheduler#242? Let's document this too somewhere? |
i think you should use this pattern anywhere you're accessing resources which are available on maven (this is one of the reasons why i'm a big advocate of putting everything there ;)). i was only aware of this case here (due to ticket links in the past), but if you have more such cases it might make sense to have a tracking issue somewhere to check everything and adapt it to simplify things? though i don't think that it's something super urgent. documenting it might make sense, though a lot of it is just standard gradle stuff. |
@rursprung I opened opensearch-project/opensearch-plugins#169, please feel free to pitch in! Thanks. |
Description
there's no need to manually construct a URL and try to fetch the artefact from there. the plugin is published on maven and we can directly use the gradle/maven dependency to fetch it.
in order to more easily identify it, a new configuration type has been added:
opensearchPlugin
.for reference see the discussions on the following issues/PRs:
Signed-off-by: Ralph Ursprung Ralph.Ursprung@avaloq.com
Issues Resolved
n/a
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.