Update the build to build.sbt style

[eed3si9n]

No description provided.

[eed3si9n]

Travis says:

*** buffer overflow detected ***: /usr/lib/jvm/java-7-openjdk-amd64/bin/java terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f760b90ee57]
/lib/x86_64-linux-gnu/libc.so.6(+0x108d50)[0x7f760b90dd50]
/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/libnet.so(Java_java_net_Inet4AddressImpl_getLocalHostName+0x190)[0x7f75f9a57960]
[0x7f7601012d98]

I even tested that it runs on Travis first https://travis-ci.org/sbt/sbinary/jobs/95235720. Travis also said "This job ran on our new platform for Legacy Precise builds. Please read our blog post for more information." so maybe the setting needs to be changed to Docker-based build. I can try to nudge that from .travis.yml.

[dwijnand]

I learnt from Seth that although using Docker is the new default, you remain on the legacy infrastructure unless you're explicit.

Should this be closed in favour of sbt#1?

[eed3si9n]

I learnt from Seth that although using Docker is the new default, you remain on the legacy infrastructure unless you're explicit.

I knew about the legacy infrastructure. It's one thing to be on legacy infrastructure, but it's another that calling java errors in "buffer overflow detected." I think it's a bug on Travis CI that happened after their recent Legacy Precise migration. See travis-ci/travis-ci#5227

Should this be closed in favour of sbt#1?

harrah/sbinary is the upstream, which currently is set to publish under org.scala-tools.sbinary organization. sbt/sbinary is a fork so I can publish it under org.scala-sbt.sbinary. Since the first thing I did was up update the build, I figured the right thing to do was to contribute my change back to the upstream.

[dwijnand]

Makes sense.

On Wed, 9 Dec 2015 21:52 eugene yokota [email protected] wrote:

I learnt from Seth that although using Docker is the new default, you
remain on the legacy infrastructure unless you're explicit.

I knew about the legacy infrastructure. It's one thing to be on legacy
infrastructure, but it's another that calling java errors in "buffer
overflow detected." I think it's a bug on Travis CI that happened after
their recent Legacy Precise migration
https://blog.travis-ci.com/2015-11-27-moving-to-a-more-elastic-future.
See travis-ci/travis-ci#5227
travis-ci/travis-ci#5227

Should this be closed in favour of sbt#1
sbt#1?

harrah/sbinary is the upstream, which currently is set to publish under
org.scala-tools.sbinary organization. sbt/sbinary is a fork so I can
publish it under org.scala-sbt.sbinary. Since the first thing I did was
up update the build, I figured the right thing to do was to contribute my
change back to the upstream.

—
Reply to this email directly or view it on GitHub
#16 (comment).