steveloughran commented on PR #14991: URL: https://github.com/apache/iceberg/pull/14991#issuecomment-3879708196
This is going to break anyone who pulls in unshaded iceberg artifacts until they add that new repo. ``` [ERROR] dependency: com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:jar:1.6.0 (test) [ERROR] com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:jar:1.6.0 was not found in https://repository.jboss.org/nexus/content/groups/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of repository.jboss.org has elapsed or updates are forced [ERROR] com.github.RoaringBitmap.RoaringBitmap:roaringbitmap:jar:1.6.0 was not found in https://repo.maven.apache.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of central has elapsed or updates are forced [ERROR] ``` What worries me is not less the change than the risk that jitpack isn't really a formal release process, more "jitpack finds and builds the right artifact when asked" Are these the official roaring bitmap artifacts, just served up to java build tools? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
