Getting rid of argparse: https://rbcommons.com/s/twitter/r/3074/

The options system is relatively new, major changes to it are low priority.

Absent a strong reason.

Screen Shot 2015-11-04 at 10.25.01 AM.png

hey guys, few questions came up in my evaluation of pants: 1) We publish our jars to an S3 bucket maven style using an sbt plugin that knows how to treat s3 like a “maven repo”. Is there something similar for pants? 2) We use an sbt plugin that creates a BuildInfo.scala file with a bunch of useful things like git commit, user, build time, java/scala version, etc. Is there a similar thing for pants? Could also put it inside the jar’s manifest instead of generating a build file. 3) Is scala’s specs2 unit testing framework supported - is there anything special beyond junit_test target I need to do?

@mysterious-action-44812: what project are you talking about? There is a staging-build pants plugin that we use to publish jars to s3. It basically just delegates to a script. See

squarepants/src/main/python/squarepants/plugins/staging_build

Sorry, thought I was at square. That plugin isn't published.

let me see...

-.txt

That plugin uses the ReplTaskMixin because there is an interactive prompt to enter credentials to upload to s3. Otherwise, the only trick to it is the

round_manager.require_data('jvm_binaries')

which forces this task to be ordered after deployable jars are created.

@mysterious-action-44812 - @ancient-stone-50795 has you on the S3 side - nothing public, Ditto BuildInfo.scala - Twitter has an in-house plugin that delivers a properties file with that sort of info. Finally, for 3 you do use a junit_tests target and then use spec2 support for running under a junit runner: http://etorreborre.github.io/specs2/guide/SPECS2-2.4.17/org.specs2.guide.Runners.html#Via+JUnit

Thanks @limited-country-20626 - I re-raised this issue offline and I think Ity has the admin keys, we'll get this sorted

@ancient-stone-50795: this is an internal project of ours at my company

@ancient-stone-50795: thanks i’ll try that, just plop it in a pants-plugins type thing?

@mysterious-action-44812: specs2 should be supported if you use the junit runner support

cool thx @witty-crayon-22786

and @enough-analyst-54434

and it's gotten ridiculously easy to inject either resources or code into the build for a target... https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/jvm/tasks/prepare_services.py is an example for resources, and for https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/codegen/tasks/ragel_gen.py generating code

well... ridiculously easy relative to how hard it use to be =P

our internal plugin for resources generates a

build.properties

file for binaries

and

org/name/build.properties

for libraries

@mysterious-action-44812: ^

with a BuildInfo.scala - alike to read these and be the in-code api

right, cool i’ll check those out

@mysterious-action-44812: You can checkout the online docs for how to setup a plugin. The code I gave you should be usable with just a few edits. http://pantsbuild.github.io/howto_plugin.html

Who knew chromium was using our fork of jmake?

Yeah - crazy

mind blown on that one

We should have just followed up with "switch to pants" for your build process. Having worked on the Chrome project, they like to go their own way from the rest of google.