Hm, maybe an unintended consequence of moving the ...
# general
i
Hm, maybe an unintended consequence of moving the pantsbuild docs, but at least one of the links in the older deprecation warnings does not exist anymore
Copy code
[ivy]17:28:16 [WARN] /root/.cache/pants/setup/bootstrap-Linux-x86_64/1.26.0_py36/lib/python3.6/site-packages/pants/engine/round_engine.py:50: DeprecationWarning: DEPRECATED: Ivy Resolve will be removed in version 1.27.0.dev0.
  resolve.ivy as well as --resolver-resolver=ivy will be removed.Please use --resolver-resolver=coursier instead and refer to <https://www.pantsbuild.org/jvm_projects.html#coursier> for setup.
  task.execute()
h
thanks for pointing that out
h
Oh, indeed. Use v1.pantsbuild.org
👍 1
h
@jolly-midnight-72759’s idea of a documentation link farm is starting to seem worth the cost.
j
🚜 ☸️ 🌽
w
or perhaps to embed the version in all URLs we render, so that they are closer to being permalinks?
h
For deprecation warnings, for sure. We can’t do that for help messages though, I think, because it might point to stale links. Or maybe we simply update all docstrings to use the new links on starting a new release series?
w
Or maybe we simply update all docstrings to use the new links on starting a new release series?
i think that that’s equivalent to doing it via a templated URL
while it’s true that linking to
v2.0
rather than
v2.1
might get you older docs, it also won’t get you a broken link for removed/renamed features/pages
more likely to be correct on average i think.
👍 1
h
Yeah, I think that’s a good call. We know sometimes users will use a particular version for several months, like some users still using 1.15-19 from last year.