I haven't read the whole thread. But I think it's fairly common sense that one should not use internal api by an external project. It's just one of life's axioms.
It's like people who use reflection to get to private members of a java class and deploy that code into production. That's just a 'quick' workaround that generates unstable products. I really cannot see any way to justify using internal api for use in a stable product beyond testing / development / exploration / proof of concept. And by extension, internal api should be subject to change and removal at any given time without prior notice. -- Leo Ufimtsev, Software Engineer, Red Hat
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
