On 2/3/2019 9:34 PM, Mark Thomas wrote:
* If this setting is still needed in some cases, is there any way to
control it without resorting to a system property? (System
properties are not very flexible, and Tomcat has many layers of more
manipulable settings, as you all would know better than me.)
No. Moving system properties to more fine-grained configuration
locations is on the TODO list.
Is there really an actual to-do list, or were you speaking
metaphorically? I'd be interested in looking at it.
I was crossing my fingers that https://github.com/apache/tomcat would
actually be using the issue tracker, and that would be the to-do list,
but I suppose I was expecting too much. Speaking of which, is the GitHub
repository the canonical place for source code? Because
https://tomcat.apache.org/svn.html claims that Tomcat still uses
Suversion and that Git is just a read-only mirror, even though
https://git.apache.org/ claims that some projects have switched to
GitHub for their primary SCM.
I'm really interested in contributing, but I shudder at thinking about
regressing a decade to start messing with Subversion (just
`.gitattributes and how it more or less fixes the CRLF nightmare is a
huge thing) and submitting patches rather than commenting on pull
requests. (I have nothing against Subversion, mind you. I thought it was
wonderful and I once used the property system extensively for per-file
metadata in a custom CRM. But for a SCM… the world has moved on.) What's
the Tomcat source code status?
Returning to the subject, do you have a list of system properties you'd
be interested in making configurable, and would this be a welcome
contribution? Where in the code code I look before committing myself?
Cheers,
Garret
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
