When env vars to be set by envinject are stored in a properties file, the following problem arises from a job's admin perspective: How is the file viewed/edited? The problem is bigger when the file is not coming from SCM, instead it just sits permanently in some location on the build server, e.g. in the same folder as the job's config.xml

Feature Request: Add to envinject the ability to show/edit in the job's configuration UI the content of a file containing env vars to be set. If it's possible, show/edit the content inline in the configuration page.