[jboss-dev] Update to jboss-cl-2.2.x stable release

[Ales Justin]

> Here is the issue that covers this> https://jira.jboss.org/jira/browse/JBAS-7661

I wouldn't go with "default" profile.

I know we already have plenty of ideas for new profiles,
but directly adding OSGi capability to "default" would probably trigger 
a flood of issues.
e.g. using some libs that have OSGi manifest, but still expecting them 
to be flat

I agree that eventually the OSGi or "more exact" CL 
description/dependencies should be default way of deploying,
just not too early -- lets have some "osgi" profile first.