Skip to content
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

Open
podile opened this issue Mar 5, 2020 · 6 comments
Open

Availability of jars in maven repo #74

podile opened this issue Mar 5, 2020 · 6 comments
Assignees
Labels
enhancement New feature or request

Comments

@podile
Copy link

podile commented Mar 5, 2020

Can the cassandra-exporter artifacts (agent,standalone) be uploaded into maven repository to enable users to embed exporter into their existing applications?

@zegelin
Copy link

zegelin commented Mar 5, 2020

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.

@podile
Copy link
Author

podile commented Mar 6, 2020

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.

@eperott
Copy link

eperott commented Mar 11, 2020

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...

Releases

@podile
Copy link
Author

podile commented Mar 12, 2020

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.

@zegelin
Copy link

zegelin commented Mar 12, 2020

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.

@zegelin zegelin self-assigned this Mar 12, 2020
@zegelin zegelin added the enhancement New feature or request label Mar 12, 2020
@kishorviswanathan
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants