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

    brainy-pilot-84216

    11/16/2016, 7:46 PM
    The pointer on how to do that is here
  • b

    brainy-pilot-84216

    11/16/2016, 7:46 PM
    @User uploaded a file: Untitled
    -.txt
  • b

    brainy-pilot-84216

    11/16/2016, 7:47 PM
    Which took me awhile to understand. But the key is the target_option //:junit
  • b

    brainy-pilot-84216

    11/16/2016, 7:48 PM
    I didn't understand what that meant and how it related to target addresses: http://www.pantsbuild.org/target_addresses.html
  • b

    brainy-pilot-84216

    11/16/2016, 7:51 PM
    So after an epiphany I realized that that is just a build target address. And the easiest way to do this is to create a build file at the root of the project that looks like:
  • b

    brainy-pilot-84216

    11/16/2016, 7:51 PM
    @User uploaded a file: Untitled
    -.txt
  • b

    brainy-pilot-84216

    11/16/2016, 7:51 PM
    Name is junit ( //:junit , the default above)
  • b

    brainy-pilot-84216

    11/16/2016, 7:52 PM
    And the jars it the new published version '1.0.16' which contains the code to allow scala tests to work
  • b

    brainy-pilot-84216

    11/16/2016, 7:52 PM
    Anyway -- this helped me understand the "language" of pants
  • w

    witty-crayon-22786

    11/16/2016, 8:06 PM
    great, thanks!
  • c

    clean-fish-15260

    11/16/2016, 8:41 PM
    so with the above, do we still use 
    junit_tests
    ? but no more need for the @RunsWith annotation on ScalaTests tests?
  • b

    brainy-pilot-84216

    11/16/2016, 8:41 PM
    Yes
  • b

    brainy-pilot-84216

    11/16/2016, 8:42 PM
    Exactly -- the code checks if the class is a scala test and if it is it automatically uses the scalatest junit runner
  • w

    witty-crayon-22786

    11/16/2016, 8:42 PM
    yea, a blurb about how to do this on the docsite would be awesome.
  • b

    brainy-pilot-84216

    11/16/2016, 8:42 PM
    Let me know where to edit and I will
  • w

    witty-crayon-22786

    11/16/2016, 8:42 PM
  • w

    witty-crayon-22786

    11/16/2016, 8:43 PM
    ...but where on the site in general...? unknown.
  • b

    brainy-pilot-84216

    11/16/2016, 8:43 PM
    probably JVM/Scala Support/Tests
  • w

    witty-crayon-22786

    11/16/2016, 8:44 PM
    @clean-fish-15260 : junit-runner 1.0.16 will also be the default in the 1.3.0dev2 and 1.2.1 releases, so
  • b

    brainy-pilot-84216

    11/16/2016, 8:45 PM
    Or even just a sentence at the top about tests
  • b

    brainy-pilot-84216

    11/16/2016, 9:08 PM
    The docs are there for review. I changed the JVM area (where it already mentioned @RunWith) and I added a tests section to the Scala area.
  • w

    witty-crayon-22786

    11/16/2016, 9:10 PM
    awesome
  • m

    mammoth-pharmacist-54215

    11/16/2016, 9:36 PM
    emeritus wfm
  • m

    mammoth-pharmacist-54215

    11/16/2016, 9:37 PM
    if i have any patches happy to go through non comiter process
  • b

    breezy-garage-85989

    11/16/2016, 11:05 PM
    okay after fighting more than i care to admit i have pants to the point that I can build a pex in preparation for multiple platforms. i added the magical incantation of
    Copy code
    platforms=[
    'linux-x86_64',
    'macosx-10.12-x86_64',
  ],
    and nothing. =[
  • b

    breezy-garage-85989

    11/16/2016, 11:06 PM
    i've nearly have exactly what is shown at http://www.pantsbuild.org/howto_develop.html#building-pants-pex-for-production but i guess i'm still missing something
  • b

    breezy-garage-85989

    11/16/2016, 11:11 PM
    if i put a bogus name in platforms no errors so something not right.
  • b

    breezy-garage-85989

    11/16/2016, 11:11 PM
  • a

    ancient-breakfast-45303

    11/16/2016, 11:17 PM
    @breezy-garage-85989 platform names are not magic
  • a

    ancient-breakfast-45303

    11/16/2016, 11:17 PM
    they are from the wheel/egg name
1...154515461547...2420Latest