I don't know if this will help you, but I'm pulling the source code of kafka down to a local machine and calling: ./sbt update /sbt -Dsbt.log.noformat=true publish-local This will publish the generated pom's and jars to your local ~/.ivy2 directory.
Once you have that, you can publish those same artifacts to your internal repo and modify your project's pom to download the artifacts from your internal repo.
That way, everyone in my group is using the same kafka artifacts that I am building. Alex Gray
It's actually a rather helpful convention SBT has instituted to deal with bytecode incompatibilities between the different versions of Scala. I wouldn't advise removing it at all - using a 2.8.0-built project in production with Scala 2.9 or higher is courting disaster.
I'm contemplating removing the '_2.8.0' bit though, since I don't think it makes sense there, more I think about it.
I replace the 'SHA' part with the actual git sha of the current build (once we have a release, I can remove the SHA part).
Jason On Tue, May 7, 2013 at 3:00 PM, Alex Zuzin <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext