Moving stuff out of jvm and into project info backend
Review Request #1917 - Created March 15, 2015 and submitted
|jsirois, patricklaw, tejal|
This is the first of a two part change to extract the IDE project info code out of the
depmap goal and into its own goal.
This change identifies tasks that reach into jvm and/or python backends but are
not really specific to the jvm backend.
Previously, these tasks were marked with TODO() with the comment 'hairball violator'
Some of these, like IDE generation, may always reach into multiple projects and may
add dependencies on C++ or other languages. Others might be able to be refactored, but
don't belong in the jvm backend either.
This change adds a README.md and necessary code changes for the new backend. Other
than that, it simply moves files from .../backend/jvm into .../backend/project_info
with only BUILD file, import changes, and removal of the hairball comments.
PANTS_DEV=1 ./pants dependencies examples/src/java/com/pants/examples/protobuf/distance PANTS_DEV=1 ./pants depmap examples/src/java/com/pants/examples/hello/main PANTS_DEV=1 ./pants eclipse examples/src/java/com/pants/examples/hello/main PANTS_DEV=1 ./pants ensime examples/src/java/com/pants/examples/hello/main PANTS_DEV=1 ./pants filedeps examples/src/java/com/pants/examples/hello/main PANTS_DEV=1 ./pants idea examples/src/java/com/pants/examples/hello/main
Nuked another TODO.
Revision 2 (+285 -227)