https://kotlinlang.org logo
Channels
Powered by
#kobalt
  • e

    evanchooly

    03/31/2016, 2:43 AM
    yeah. i need to bump that.
  • c

    cedric

    03/31/2016, 2:44 AM
  • c

    cedric

    03/31/2016, 2:46 AM
    Here is what I get:
    Copy code
    Couldn't find C:\Users\cbeust\.kobalt\wrapper\dist\kobalt-0.716\kobalt\wrapper\kobalt-0.716.jar, using
  C:\Users\cbeust\kotlin\kobalt\out\production\kobalt C:\Users\cbeust\kotlin\kobalt\out\production\kobalt-plugin-api C:\Users\cbeust\kotlin\kobalt\out\production\kobalt-wrapper
  • c

    cedric

    03/31/2016, 2:46 AM
    (specifying 
    0.716
    in 
    kobalt.properties
    )
  • c

    cedric

    03/31/2016, 2:47 AM
    Note that Kobalt automagically adds all its own module directories for a flawless experience
  • e

    evanchooly

    03/31/2016, 2:47 AM
    😄
  • c

    cedric

    03/31/2016, 2:48 AM
    Would love your feedback about what it's like to go through all this, it's second nature to me but it might be overwhelming for newcomers, happy to improve
  • c

    cedric

    03/31/2016, 2:49 AM
    Bit hard to keep the complexity in check given everything that happens under the cover: class loading everywhere, configuration files, multi projects interacting with each other, ...
  • e

    evanchooly

    03/31/2016, 2:50 AM
    yeah. and there’s something fundamentally odd about working on a build tool. the lifecycle gets a bit odd here and there.
  • e

    evanchooly

    03/31/2016, 2:50 AM
    so far it’s not bad.
  • c

    cedric

    03/31/2016, 2:50 AM
    Happy to hear it
  • c

    cedric

    03/31/2016, 2:50 AM
    And yes, working on what I call "fundamental" stuff (code that sits at the very bottom of the tech stack) can be challenging
  • e

    evanchooly

    03/31/2016, 2:51 AM
    -.sh
    -.sh
  • c

    cedric

    03/31/2016, 2:51 AM
    Maybe the out directory is not 
    out
    ?
  • c

    cedric

    03/31/2016, 2:51 AM
    Project structure / output dir
  • e

    evanchooly

    03/31/2016, 2:51 AM
    the out directory of what, though?
  • e

    evanchooly

    03/31/2016, 2:52 AM
    i get that on the CLI, too, when using 
    java -jar
    unless i specified the 
    KOBALT_JAR
    variable
  • c

    cedric

    03/31/2016, 2:52 AM
    Project Structure / Project / Project Compiler output
  • c

    cedric

    03/31/2016, 2:52 AM
    Let's see where IDEA compiles its classes
  • c

    cedric

    03/31/2016, 2:52 AM
    Me it's 
    C:\Users\cbeust\kotlin\kobalt\out
  • e

    evanchooly

    03/31/2016, 2:53 AM
    /Users/jlee/personal/dev/kotlin/kobalt/out
  • c

    cedric

    03/31/2016, 2:54 AM
    Yeah let's make this match what kobalt expects
  • c

    cedric

    03/31/2016, 2:54 AM
    Bit rigid right now, sorry
  • c

    cedric

    03/31/2016, 2:54 AM
    Down the line, Kobalt could try to dig these settings from some 
    .idea/
    file
  • e

    evanchooly

    03/31/2016, 2:55 AM
    what should it be? the other project shouldn’t care and that path is, of course, visible to the build process...
  • c

    cedric

    03/31/2016, 2:55 AM
    Should be 
    /Users/jlee/kotlin/kobalt/out
  • c

    cedric

    03/31/2016, 2:56 AM
    Remember you're just seeing this because you specified a nonexistent version, something only Kobalt devs will ever see
  • c

    cedric

    03/31/2016, 2:56 AM
    You should put kobalt in 
    ~/kotlin/kobalt
  • e

    evanchooly

    03/31/2016, 2:56 AM
    and I set that in my kobalt’s project seeting?
  • e

    evanchooly

    03/31/2016, 2:56 AM
    oh. so I should move my kobalt workspace entirely?
1...315316317...826Latest