Hi, I've just changed something in POILogger for #58040 and additionally refactored the various methods to a varags method. This works when code gets compiled but fails if only the binary is replaced.
What is our guideline regarding ...? - binary compatibility - deprecated objects, i.e. org.apache.poi.openxml4j.opc.Package Nicks posts [1] says: "Backwards compatibility - if possible we maintain binary compatibility, if not source, and only break things if really needed." So binary compatibility means our dependencies? and "if not source" means, it's ok when user code doesn't need to be changed, but needs to be recompiled? How about allowing to remove deprecated stuff after 2 years (i.e. ages) after it has been marked deprecated? Regarding the POILogger - I sometimes wonder, why we need to keep (historical) things which in the meantime exist in common. How about replacing POILogger by SLF4J? (it seems to be compatible with ASL [2]) Best wishes, Andi [1] http://apache-poi.1045710.n5.nabble.com/Advice-for-new-and-potential-committers-td5718862.html [2] http://www.slf4j.org/license.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
