Use ClassName as Name of OSGi component

Description

This ticket will implement a wew naming convention for OSGi component - use the fully qualified implementation class name as component name. Compare to the previous all lowercase arbitrary naming convention, the new approach is a lot easier for core and extension developer to follow and remove the hassle to figure out the purpose of a component from its arbitrary name.

Environment

None

Activity

Fixed

Details

Assignee

Reporter

Components

Priority

Created July 31, 2013 at 8:28 AM
Updated March 13, 2014 at 2:19 PM
Resolved July 31, 2013 at 3:11 PM