Update pants and pants.toml for 2.0 release

[danieljanes]

This PR is in preparation for the Pants 2.0.0 release. It's in draft mode because 2.0 is not stable yet, but it could be merged once that changes.

The PR is intended to
(a) serve as a working example for people who want to explore Pants 2.0
(b) show the diff between a working 1.x and 2.0 configuration

Progress:

• Right now, the upgrade to 2.0.0.dev4 still fails: ./pants list :: raises 31 rules errors - any feedback is appreciated
• Update: According to @stuhood the failure seems to be related to protoc not being ready for 2.0 yet (Loading pants.backend.codegen.protobuf.python fails in dev releases pants#10425)
• Update 2: Downgrading to 2.0.0.dev2 fixed the issue
• Update 3: The new 2.0.0.dev5 fixes the regression, everything seems to work on the latest dev release now

[Eric-Arellano]

Thank you! Could you please apply this diff as well to update ./pants_from_sources?

diff --git a/pants_from_sources b/pants_from_sources
index 08de322..733aae1 100755
--- a/pants_from_sources
+++ b/pants_from_sources
@@ -36,10 +36,10 @@ function string_list() {
 }

 export PANTS_VERSION="$(cat "${PANTS_SOURCE}/src/python/pants/VERSION")"
-export PANTS_PLUGINS2="$(string_list plugins)"
+export PANTS_PLUGINS="$(string_list plugins)"
 export PANTS_PYTHONPATH="+$(string_list pythonpath)"
-export PANTS_BACKEND_PACKAGES2="+$(string_list backend_packages)"
-export PANTS_ENABLE_PANTSD="${ENABLE_PANTSD}"
+export PANTS_BACKEND_PACKAGES="+$(string_list backend_packages)"
+export PANTS_PANTSD="${ENABLE_PANTSD}"
 export no_proxy="*"

 exec "${PANTS_SOURCE}/pants" "--no-verify-config" "$@"

[danieljanes]

Thank you! Could you please apply this diff as well to update ./pants_from_sources?

diff --git a/pants_from_sources b/pants_from_sources
index 08de322..733aae1 100755
--- a/pants_from_sources
+++ b/pants_from_sources
@@ -36,10 +36,10 @@ function string_list() {
 }

 export PANTS_VERSION="$(cat "${PANTS_SOURCE}/src/python/pants/VERSION")"
-export PANTS_PLUGINS2="$(string_list plugins)"
+export PANTS_PLUGINS="$(string_list plugins)"
 export PANTS_PYTHONPATH="+$(string_list pythonpath)"
-export PANTS_BACKEND_PACKAGES2="+$(string_list backend_packages)"
-export PANTS_ENABLE_PANTSD="${ENABLE_PANTSD}"
+export PANTS_BACKEND_PACKAGES="+$(string_list backend_packages)"
+export PANTS_PANTSD="${ENABLE_PANTSD}"
 export no_proxy="*"

 exec "${PANTS_SOURCE}/pants" "--no-verify-config" "$@"

Done

[Eric-Arellano]

Thank you @danieljanes for iterating on this! Looks great. Right now, it's targeted to merge into the master branch. I pushed a new branch called 2.0. Could you please change this PR to merge into 2.0? I'm not sure if you can change that when already created - it may require creating a new PR.

[danieljanes]

Thank you @danieljanes for iterating on this! Looks great. Right now, it's targeted to merge into the master branch. I pushed a new branch called 2.0. Could you please change this PR to merge into 2.0? I'm not sure if you can change that when already created - it may require creating a new PR.

Thanks @Eric-Arellano! I've changed the target to 2.0 (it's possible to do this on existing PRs). Since we have the 2.0 branch target I've also updated the state from "draft" to "ready for review".

[Eric-Arellano]

Thank you!