So, the typical concern here is that using something like `${version.commons.pool}`, rather than a range, locks users into having to use that explicit version, even if something newer comes out that's backwards compatible.  Generally, the ranges are considered to be a good thing, but that's your call.  Thoughts?

The other big issue is that the Maven artifact version frequently != the OSGi exported package version.  For instance, you might see the artifact using 1.2.3.Final, but the exported packages using "1.2.3" or even "1.2".  I honestly can't remember what ".Final" does if used for an exported version.  But, regardless, the point is that you could potentially be introducing lots of pain points.