Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312799

Summary:	[releng] Rename external libraries into the ecf namespace
Product:	Community	Reporter:	Wim Jongman <wim.jongman>
Component:	Cross-Project	Assignee:	David Williams <david_williams>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	bugs.eclipse.org, david_williams
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Wim Jongman

2010-05-13 10:41:12 EDT

Markus Kuppe suggested in bug 312793:

In general we might want to consider moving all our source bundles into the "org.eclipse.ecf" namespace. E.g. "org.eclipse.ecf.org.apache.zookeeper". This not only saves us from bloated cqueries/mspecs (and fragile builds in general), but also from accidental collisions with other versions of 3rd party binaries. This technique is for example used by the SpringSource bundle repository.

This pattern should be used before external libraries move to orbit

Comment 1 David Williams

2012-06-17 00:53:23 EDT

In general, it'd be wrong to "change namespace" of external libraries, and would only make sense if there were known problems or conflicts. Otherwise we should strive for community consistency and collaboration. I think SpringSource had their reasons for doing what they did, but it was more for "non standard" reasons, whereas most of what we do (at least in Orbit) follows the OSGi standard. Again, there might be occasional exceptions ... but ... since they would be exceptions, we don't need a general rule about it. 

Thanks for your suggestions.