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

Please upload to Maven Central #73

Open
silentkid86 opened this issue Jan 13, 2017 · 4 comments
Open

Please upload to Maven Central #73

silentkid86 opened this issue Jan 13, 2017 · 4 comments

Comments

@silentkid86
Copy link

Hi,

I am trying to use Chronos, which depends on this particular project. Can you upload this artifact to Maven Central instead of using a proprietary Maven repo ?

@doruchiulan
Copy link

doruchiulan commented Dec 19, 2019

Also, I see latest releases are not in your maven repository. Last is 0.6.0 I think

PS. Found them, artifact names also contain scala versions (e.g. 0.8.8 is chaos_2.11, 0.9.0 is chaos_2.12)

@strowk
Copy link

strowk commented Oct 9, 2020

Hello! Is this project alive? If we to use it, it should be in central (otherwise our mirror won't download it), so I wanted to check on that issue here.

@DominikDary
Copy link

Hi @strowk, right now this project is only used in one project which is soon to be deprecated.
Having said this we have no plans to bring this to maven central.

@rwolfson
Copy link

Hi,
Just noting that it looks like the downloads.mesosphere.io and downloads.mesosphere.com domains no longer seem to exist in DNS, so Chronos will no longer build using Maven; similar to the concern of the original poster above. The former is currently listed in this project's README.md as a suggested way of getting Chaos via Maven.

Is anyone aware of an alternate public place to get these artifacts right now? If not, would D2iQ (Mesosphere) be open to either reactivating those domains, or sharing the final Maven file tree another way for interested parties to archive to their own private S3 buckets?

I can see that although the domains don't exist anymore, the same names exist as S3 buckets with the website feature disabled; the error message here is different than a non-existent bucket or referencing the wrong AWS region.

~$ host downloads.mesosphere.io
Host downloads.mesosphere.io not found: 3(NXDOMAIN)
~$ host downloads.mesosphere.com
Host downloads.mesosphere.com not found: 3(NXDOMAIN)
~$ curl -s http://downloads.mesosphere.io.s3-website.us-east-1.amazonaws.com | grep Message
<li>Message: The specified bucket does not have a website configuration</li>
~$ curl -s http://downloads.mesosphere.com.s3-website.us-east-1.amazonaws.com | grep Message
<li>Message: The specified bucket does not have a website configuration</li>

I opened up a related ticket under the Chronos repo, as well mesos/chronos#906

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

No branches or pull requests

5 participants