-
Notifications
You must be signed in to change notification settings - Fork 46
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
Availability of jars in maven repo #74
Comments
Can't see why not. Though I was always under the impression that Maven Central was for libraries (Guava, Guice, etc) rather than apps. Can you expand on the use case a bit? What app are you trying to embed the exporter inside? I'll see if it's possible to integrate this into the CI pipeline. |
We have already installed our own standalone agent app for each node to perform day-to-day maintenance on the node (like monitoring critical metrics, cleaning snapshots, restarting node etc). Making the exporter jars available in central repo enables us to embed the exporter-functionality into our existing app instead of running a new java process for stand-alone exporter. |
I'm +1 to keep dependencies like this in Maven repos, simply because there are so many tools that will automate dependency management for me with proper Maven coordinates. But @zegelin have been publishing all releases directly on GitHub which makes it easy to get artifacts from a predictable URL in your automation. So, there is no need to build things on your own, unless you have a fork with modifications. Just wanted to mention it... |
The current published jar is very fat(9 MB) and many of the classes in the current jar(like netty, datastax etc ) are already used in my current application. If we can publish the other jar standalone- (~35KB) to maven, it can be integrated easily into current app. |
I'll look to extending the CI pipeline to push the built, pre-shaded JARs up to Maven Central or somewhere similar. I have a bit of bandwidth to look into this over the next few days. |
We have our database servers disconnected from the internet and we have an internal mirror for maven. It would be nice if you could publish the jars to maven as well, so we don't have to manually host it on our mirror. |
Can the cassandra-exporter artifacts (agent,standalone) be uploaded into maven repository to enable users to embed exporter into their existing applications?
The text was updated successfully, but these errors were encountered: