Compiled 2015-07-22T12:07
build.eclipse.org
- Usage exceeding 1GB for: Hudson master jobs and workspace (2015-07-22T10:00)
2.8G papyrus-trunk-nightly
2.3G ep45I-unit-lin64
2.1G ep46N-unit-lin64
1.6G ep45N-unit-lin64
1.5G ep45N-unit-mac64
1.5G ep45N-unit-win32
1.5G
Konstantin,
let me send this at the beginning: this discussion is greatly appreciated -
although my personal answer might not be satisfying yet…
Library projects like Sapphire or Nebula are somewhat special because they are
(more or less) exclusively used by third-party plugins. Hence they do
My proposal:…
Sounds okay to me. I wonder if the short cut „not to enable 3rd party class
names in stack traces by default“ would be acceptable as well since it’s right
on the configure dialog and easy to grasp (IMHO).
Wayne,
any thoughts on this? I can change the defaults (for SR1) if the
I assume that you and everyone else understands why classnames from
non-eclipse/non-apache bundles are replaced by HIDDEN.HIDDEN by default.
I can imagine cases, such as pre-release products and internal solutions, where
stack frames contain sensitive information, but that isn’t the
Hi
IMHO, the 20% who explicitly enabled message anonymization will also
enable method anonymization because they are avoiding the problem of
needing corporate approval of any release of data. A method name such as
SHA4096 may reveal what algorithm is being exploited/developed. Too
risky if
