-
Notifications
You must be signed in to change notification settings - Fork 529
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
build failed for chronos #68
Comments
It's likely that Mesos 0.14.0 will be tagged from master of the Mesos source tree. You can probably get the build working by matching the version of Mesos you have running with the jar that gets generated and modifying the Chronos dependency in the POM. <dependency>
<groupId>org.apache.mesos</groupId>
<artifactId>mesos</artifactId>
<version>0.12.0-SNAPSHOT</version>
</dependency> For example I've got v0.12.0 running and I noticed that the Chronos build installs a SNAPSHOT build of the Mesos Java library. |
FYI - this issue has been resolved with the latest commit made to master. Maven now resolves the Apache Mesos dependency from a public Maven repo - <repository>
<id>mesosphere-public-repo</id>
<name>Mesosphere Public Snapshot Repo</name>
<url>http://s3.amazonaws.com/mesosphere-maven-public/snapshot/</url>
</repository> |
Yes, this should be fixed as of now. Sorry for the inconvenience. We restructured our maven repo! |
Using Sun Java 7. Mesos is already installed. This is the message I get:
Could not resolve dependencies for project com.airbnb:chronos:jar:1.0-SNAPSHOT: Could not find artifact org.apache.mesos:mesos:jar:0.14.0 in twitter-repo (http://maven.twttr.com/)
The text was updated successfully, but these errors were encountered: