Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 22 2015 11:10
    japgolly commented #2066
  • Jun 22 2015 08:25
    keepscoding commented #2044
  • Jun 21 2015 03:24
    xerial commented #157
  • Jun 21 2015 00:10
    eed3si9n unlabeled #2057
  • Jun 21 2015 00:10

    eed3si9n on 0.13

    Adds bundledLauncherProj to all… Remove launcher tests Add unit tests to Travis and 3 more (compare)

  • Jun 21 2015 00:10
    eed3si9n closed #2057
  • Jun 21 2015 00:10

    eed3si9n on fixbuild

    (compare)

  • Jun 20 2015 18:42
    eed3si9n synchronize #2057
  • Jun 20 2015 18:42

    eed3si9n on fixbuild

    Fix typo (compare)

  • Jun 20 2015 18:23

    eed3si9n on fixbuild

    Adds bundledLauncherProj to all… Remove launcher tests Add unit tests to Travis and 1 more (compare)

  • Jun 20 2015 18:23
    eed3si9n synchronize #2057
  • Jun 20 2015 14:59

    eed3si9n on scalaversionbump

    (compare)

  • Jun 20 2015 14:59

    eed3si9n on 0.13

    Bumping up Scala version to 2.1… Try to keep bincompat Fixes #1666 and 1 more (compare)

  • Jun 20 2015 14:59
    eed3si9n unlabeled #2068
  • Jun 20 2015 14:59
    eed3si9n closed #2068
  • Jun 20 2015 14:59
    eed3si9n closed #1666
  • Jun 20 2015 14:57
    eed3si9n commented #2068
  • Jun 20 2015 12:55
    dwijnand commented #2068
  • Jun 20 2015 04:51
    eed3si9n synchronize #2068
  • Jun 20 2015 04:51

    eed3si9n on scalaversionbump

    Fixes #1666 (compare)

Sukant Hajra
@shajra
Also, I just realized I don't know the best way to set a global setting in a .sbt file. Is that possible? It seems like all the settings in a .sbt file seem set at the project level.
Sukant Hajra
@shajra
hmm... using "inThisBuild" inside the project-level settings seems really counter-intuitive to me: http://www.scala-sbt.org/0.13/docs/Scopes.html#Build-level+settings
But I guess it works because it removes a "This" out of the key references, which essentially makes it no-longer a candidate for project-level scoping.
Dale Wijnand
@dwijnand
Yeah you replace the implicit, unresolved This axis value with the alternative, also unresolved, ThisBuild axis value. I tend not to nest it inside the root project's settings and just declare it at the root because it's unnecessary nesting.
Sukant Hajra
@shajra
okay, makes sense.
It's good to hear these things out loud from another person.
Gerard Vico
@HDBandit
hello guys
I have a question about the integration with an internal proxy for dependencies. I installed artifactory, and I am working with sbt. Sbt remains resolving a lot of time. I am monitoring the artifactory logs, and I don¡'t see accesses to the artifactory. What SBT is doing when is resolving?
OlegYch
@OlegYch
nothing useful
try sbt-coursier
Krishna Padmasola
@kpadmasola

Hi, I am trying to run some gatling simulations via sbt, but I am getting this error:

[error] Uncaught exception when running tests: java.lang.NoSuchMethodError: scala.Predef$.refArrayOps([Ljava/lang/Object;)Lscala/collection/mutable/ArrayOps;
sbt.ForkMain$ForkError: java.lang.NoSuchMethodError: scala.Predef$.refArrayOps([Ljava/lang/Object;)Lscala/collection/mutable/ArrayOps;
        at io.gatling.sbt.GatlingRunner.tasks(GatlingRunner.scala:30)
        at sbt.ForkMain$Run.runTests(ForkMain.java:253)
        at sbt.ForkMain$Run.run(ForkMain.java:139)
        at sbt.ForkMain.main(ForkMain.java:121)

any pointers on how to resolve this error ?

Thomas Sutton
@thsutton
Maybe you have a plugin and an SBT build that were built against different versions of Scala?
Krishna Padmasola
@kpadmasola

@thsutton I am using these plugins:

> plugins                                                                
In file:/E:/perf/                                     
        sbt.plugins.IvyPlugin: enabled in perf                           
        sbt.plugins.JvmPlugin: enabled in perf                           
        sbt.plugins.CorePlugin: enabled in perf                          
        sbt.plugins.JUnitXmlReportPlugin: enabled in perf                
        sbt.plugins.Giter8TemplatePlugin: enabled in perf                
        com.typesafe.sbteclipse.plugin.EclipsePlugin: enabled in perf    
        coursier.CoursierPlugin: enabled in perf                         
        io.gatling.sbt.GatlingPlugin: enabled in perf

in build.sbt I have scalaVersion := "2.12.2"
how do I find out which plugin is incompatible with this version of scala ?

Krishna Padmasola
@kpadmasola
@thsutton figured it out by looking at https://github.com/gatling/gatling-sbt-plugin-demo/blob/master/build.sbt. I changed scalaVersion := "2.11.8" in my build.sbt and the error is gone. Thanks!
Sukant Hajra
@shajra
Is the "requires" field of an AutoPlugin used at all if the "trigger" is set to "noTrigger"? I think I understand how it's used when the trigger is set to "allRequirements".
Thomas Sutton
@thsutton
@kpadmasola No worries. It's a rare question in here that I can try to help with. :-)
eugene yokota
@eed3si9n
@shajra without requires your plugin will load at quasi random order potentially before all the sbt default settings
Sukant Hajra
@shajra
This message was deleted
Han van Venrooij
@irundaia

Hi guys,

I've got an issue where I package a native lib in a jar along with my sbt plugin. When the user of the plugin has a different version on his machine, there is the possibility for linking issues when the library is loaded with Native.loadLibrary.
Do you know of a way to force loading the library from the jar?

Oron Port
@soronpo
How do I remove options of scalacOptions by pattern matching?
Dale Wijnand
@dwijnand
Such as?
Oron Port
@soronpo
I have
... "-Xplugin:/home/soronpo/.ivy2/cache/org.scalamacros/paradise_2.12.2/jars/paradise_2.12.2-2.1.0.jar", ... "-Xplugin:/home/soronpo/.ivy2/cache/org.scalameta/paradise_2.12.2/jars/paradise_2.12.2-3.0.0-M9.jar" ... and want to just remove .*paradise.*
Dale Wijnand
@dwijnand
scalacOptions ~= { opts => ... }
Oron Port
@soronpo
What does ~= do? I cannot find documentations for it
Dale Wijnand
@dwijnand
modifies the value of the key
Hmm, wow, we really don't have ~= in the docs
Oron Port
@soronpo
@dwijnand I'm sorry, but I still don't follow. How does this allow me to remove the specific settings?
Here is my setting. I want to remove the entries which have paradise in their value.
[info] * -deprecation
[info] * -encoding
[info] * UTF-8
[info] * -feature
[info] * -language:existentials
[info] * -language:experimental.macros
[info] * -language:higherKinds
[info] * -language:implicitConversions
[info] * -unchecked
[info] * -Xfatal-warnings
[info] * -Xfuture
[info] * -Xlint:-unused,_
[info] * -Yliteral-types
[info] * -Yno-adapted-args
[info] * -Ywarn-numeric-widen
[info] * -Xplugin-require:macroparadise
[info] * -Xplugin:/home/soronpo/.ivy2/cache/org.scalamacros/paradise_2.12.2/jars/paradise_2.12.2-2.1.0.jar
[info] * -Xplugin:/home/soronpo/.ivy2/cache/org.scalameta/paradise_2.12.2/jars/paradise_2.12.2-3.0.0-M9.jar
Dale Wijnand
@dwijnand
Sorry, @soronpo, got distracted. scalacOptions ~= (_ filterNot (_ contains "paradise"))
Though really I think you should fix the upstream issue of having different paradise plugins in your build
Oron Port
@soronpo
@dwijnand It's a workaround, since meta isn't currently working in REPL. So actually I'll be doing scalacOptions in (Compile, console) ~= (_ filterNot (_ contains "paradise")).
Dale Wijnand
@dwijnand
gotcha
Oron Port
@soronpo
??
missing parameter type for expanded function ((x$1) => x$1.filterNot(((x$2) => x$2.contains("paradise"))))
scalacOptions in (Compile, console) ~= (_ filterNot (_ contains "paradise"))
^
Dale Wijnand
@dwijnand
scalameta/paradise#10 ?
Oron Port
@soronpo
scalameta/paradise#10 ?
yes
Dale Wijnand
@dwijnand
That message is confusing
worked in my mini repro
Oron Port
@soronpo
OK, my bad. Forgot a comma somewhere .
Yes! Works like a charm. Many thanks.
Dale Wijnand
@dwijnand
cool
Sukant Hajra
@shajra
@eed3si9n question about sbt-doge. Would enabling it with an AutoPlugin on all projects (not just an aggregate root) be a bad idea?
Sorry, I mean CrossCompilePerProjectPlugin.
Jose C
@jmcardon
Hey guys, is sbt-onejar the preferred way of packaging?
Adelbert Chang
@adelbertc
@jmcardon i think sbt-onejar is no longer maintained is it? sbt-assembly seems to be the way to go. also less classloader voodoo
Sukant Hajra
@shajra
I just looked at the sbt-coursier project. Maybe I'm a bit dense, but which problem does it solve that people find most useful? Resolutions taking a while?
Ghost
@ghost~540393fe163965c9bc2018ce
is there an option that when a macro is changed, all downstream code is marked dirty?
it's really hard to find it given that most google for "sbt macro incremental compiler" give completely the wrong thing
Jorge
@jvican
yes, there's a way.
and it's been proven to work well. i would like to try to merge it in the future inside Zinc (in a minor release, after sbt 1.0) @fommil
have a look at Martin Duhem's thesis on incremental macro compilation https://infoscience.epfl.ch/record/204855/files/MacrosInSbtProblemSolved.pdf