Record the compile classpath used to compile jvm targets.

Review Request #3576 - Created March 16, 2016 and submitted

Information
Garrett Malmquist
pants
gmalmquist/compile-classpath-records
3050
Reviewers
pants-reviews
benjyw, nhoward_tw, stuhood, zundel
This change makes `jvm_compile` write text files storing the
classpath for each jvm target it compiles to:

    .pants.d/compile/zinc/<sha>/<target.id>/<sha>/classes/compile_classpath/<target.id>.txt

Since these files are written to the classes/ directory, they end
up being bundled into jvm binaries. This can be useful to determine
how an artifact was built after the fact.

This behavior is enabled by default, and can be disabled with:

    --no-compile-zinc-capture-classpath

Added tests to tests/python/pants_test/backend/jvm/tasks/jvm_compile/java/test_zinc_compile_integration.py.

CI went green here: https://travis-ci.org/pantsbuild/pants/builds/116469638
CI went green here: https://travis-ci.org/pantsbuild/pants/builds/116666267

Issues

  • 0
  • 2
  • 0
  • 2
Description From Last Updated
Nick Howard (Twitter)
Eric Ayers
Eric Ayers
Eric Ayers
Garrett Malmquist
Garrett Malmquist
Review request changed

Status: Closed (submitted)

Change Summary:

In commit ff02fbdfe1047ef6356255834b906a7c753589bf. Thanks Nick & Eric!

Benjy Weinberger
Ship It!
Loading...