-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[BUG] Main branch does not pull 9.1.0-snapshot-ea989fe8f30 to m2 after deploying mavenlocal #2500
Comments
Seems like this is caused by 1st time we use anything that is not officially on lucene maven repo. @nknize @dblock please confirm. Thanks. |
Hi @peterzhuamazon, We can fix this by updating common-utils to apply the It would be nice to publish these lucene snapshots to |
Why aren't we using official Lucene builds/snapshots? https://lucene.apache.org/core/developer.html. Is that what @mch2 Do you have time to look into this? |
Learned this from @nknize - The official Lucene snapshots build each artifact separately after commit. So each artifact is built with a separate sha and at a different time. Our build system right now locks to a single sha in version.properties Either way, we should update common-utils to add the repositories plugin, have made a PR over there. |
@peterzhuamazon Did this resolve your issue? are there other repos with the same problem? |
@mch2 I have tested on 2.0.0 build this morning and it passed. |
Run this on main branch of OpenSearch core as of
b9f04405d6dfabcc2b8e87a86d4f83b003b3ffe7
Check
~/.m2/repository/org/apache/lucene/lucene-core
, 9.1.0-snapshot-ea989fe8f30 not exist.This cause things after core such as common-utils to fail to these msg:
Logs
The text was updated successfully, but these errors were encountered: