gecko-dev/python
Gregory Szorc 5dd371e131 Bug 1376306 - Update tests to reflect new Java version requirement; r=me
f497b6194e9f bumped the minimum Java version requirement in configure
from 1.7 to 1.8. It forgot to update tests that were pinning the
Java version at 1.7. The tests then failed.

We bump the versions in tests to restore order.

CLOSED TREE

MozReview-Commit-ID: 1zm5L1QQy7a

--HG--
extra : rebase_source : 8868224b5a1a8ffbb633b638df9485760f84fd8a
extra : amend_source : 3faa435ab5478c62aefb3dc18de19256ce0d906e
2017-07-28 17:40:00 -07:00
..
devtools/migrate-l10n Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
mach Bug 1172574 - Allow for setting prefs in mach run for scratch_user;r=gps 2017-07-28 15:38:22 -07:00
mozboot Bug 1255227 - Pre: Use {0} for Python 2.6. r=sebastian 2017-07-25 14:46:53 -07:00
mozbuild Bug 1376306 - Update tests to reflect new Java version requirement; r=me 2017-07-28 17:40:00 -07:00
mozlint Bug 1361972 - [mozlint] Add ability to only lint staged changes to --workdir with git r=standard8 2017-06-30 18:29:31 -07:00
mozversioncontrol/mozversioncontrol Bug 1377216 - Use configure-derived VCS info to find repository; r=glandium 2017-07-18 15:46:47 -07:00
mach_commands.py Bug 1048446 - [python-test] Add 'sequential' key to python.ini manifests so tests can opt out of running in parallel, r=jmaher 2017-06-01 09:50:15 -04:00
moz.build Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
README Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00

This directory contains common Python code.

The basic rule is that if Python code is cross-module (that's "module" in the
Mozilla meaning - as in "module ownership") and is MPL-compatible, it should
go here.

What should not go here:

* Vendored python modules (use third_party/python instead)
* Python that is not MPL-compatible (see other-licenses/)
* Python that has good reason to remain close to its "owning" (Mozilla)
  module (e.g. it is only being consumed from there).

Historical information can be found at
https://bugzilla.mozilla.org/show_bug.cgi?id=775243
https://bugzilla.mozilla.org/show_bug.cgi?id=1346025