https://pantsbuild.org/ logo
Powered by
#general
  • w

    witty-crayon-22786

    07/20/2017, 6:45 PM
    to publish jars (to maven central, or artifactory, or your local .m2 directory), you'd use 
    ./pants publish
  • m

    mysterious-farmer-45668

    07/20/2017, 6:45 PM
    ah okay
  • m

    mysterious-farmer-45668

    07/20/2017, 6:46 PM
    we're converting from a maven shop... so people want jars to be created from targets which don't have a main
  • w

    witty-crayon-22786

    07/20/2017, 6:46 PM
    @mysterious-farmer-45668 : for which purpose
  • w

    witty-crayon-22786

    07/20/2017, 6:46 PM
    publishing, or deployment
  • m

    mysterious-farmer-45668

    07/20/2017, 6:46 PM
    for publishing to repositories and such, I think.
  • w

    witty-crayon-22786

    07/20/2017, 6:47 PM
    ok; worth figuring out exactly.
  • w

    witty-crayon-22786

    07/20/2017, 6:47 PM
    publishing is not strictly necessary in a monorepo
    ✨ 1
  • w

    witty-crayon-22786

    07/20/2017, 6:48 PM
    the vast majority of code at twitter is just packaged as deploy binaries and then shipped that way
  • m

    mysterious-farmer-45668

    07/20/2017, 6:48 PM
    ok. sounds good
  • w

    witty-crayon-22786

    07/20/2017, 6:49 PM
  • w

    witty-crayon-22786

    07/20/2017, 6:50 PM
    and http://www.pantsbuild.org/publish.html describes versioned publishing
  • m

    mysterious-farmer-45668

    07/20/2017, 6:53 PM
    thanks!
  • w

    witty-crayon-22786

    07/20/2017, 7:55 PM
    is anyone still using scala 2.10 with pants?
  • w

    witty-crayon-22786

    07/20/2017, 7:55 PM
  • r

    rough-minister-58256

    07/20/2017, 8:02 PM
    not I
  • r

    rough-dog-96241

    07/21/2017, 12:16 AM
    Curious if node 7/8 is of any interest to pants people? I see there's support for 6.x and was wondering about the backstory?
  • w

    witty-crayon-22786

    07/21/2017, 12:21 AM
    cc @brash-cricket-7489 : ^
  • w

    witty-crayon-22786

    07/21/2017, 12:22 AM
    should work just fine. iirc, a binary build exists, but @brash-cricket-7489 was waiting for more internal testing before we merged it to https://github.com/pantsbuild/binaries
  • w

    witty-crayon-22786

    07/21/2017, 12:23 AM
    or maybe i'm misremembering. regardless, that's the process for uploading a new one, if you'd like to.
  • r

    rough-dog-96241

    07/21/2017, 12:24 AM
    Oh okay, cool. 👍
  • p

    purple-oil-45048

    07/21/2017, 12:40 AM
    @mysterious-farmer-45668 do you have a plan in mind how to convert a maven shop into a pants shop?
  • m

    mysterious-farmer-45668

    07/21/2017, 4:06 AM
    I don't have a specific plan, but right now all of the new projects are going into pants. After people get the grasp of how to do things in pants, the plan is to migrate over existing maven code
  • m

    mysterious-farmer-45668

    07/21/2017, 4:09 AM
    but people seem to expect the same things to be available across different build tools. which is kind of a headache for me to explain every time
  • p

    purple-oil-45048

    07/21/2017, 4:25 AM
    thanks! besides the build-tool itself, are you also starting the new projects in a mono-repo? I find this to be much more difficult to convince people to adopt ..
  • m

    mysterious-farmer-45668

    07/21/2017, 4:19 PM
    yeah, i can't lie and say that it's easy... i find people sort of developed a stockholm syndrome for bad processes and developing over 100+ maven projects, they think there's no problem with it- but when I sit down with them and show them that thing don't have to be that way, they are convinced. so it takes a lot of 1:1 meetings.
  • f

    fancy-queen-20734

    07/21/2017, 4:30 PM
    That’s awesome. Have you noticed any common patterns around what convinces people?
  • m

    mysterious-farmer-45668

    07/21/2017, 4:38 PM
    With excessive maven project creation/consumption within one large group, (I think) some dependency hell is bound to happen- and it's happened within my org. The problems that our org experiences can be solved by having a shared code repository. For example
  • m

    mysterious-farmer-45668

    07/21/2017, 4:39 PM
    there's this one massive "shared" jar that every project has to inherit- but when this shared jar gets updated, it doesn't promise backward compatibility and all the children projects are not forced to update
  • m

    mysterious-farmer-45668

    07/21/2017, 4:39 PM
    but all people want to actually do is use the shared code
1...178317841785...2420Latest