Yes, we should clean it up. I just did a clean up on the camel-cxf pom.xml it should not mark the OSGi related dependencies as provided now.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Monday, March 4, 2013 at 9:38 PM, Claus Ibsen wrote: > Hi > > Just noticed that the camel-cxf dependency is rather long. > > Anyway why is OSGi blueprint pulled in as mandatory dependencies? eg > aries blueprint etc. > IMHO all the OSGi pieces should be optional / provided so non-OSGi > users can use the maven dependencies without pulling in unwanted > dependencies. > > What we usually do is to have osgi code in .osgi packages so they are > hidden for non OSGi users. So the classloader will not attempt to load > them in non OSGi environments. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com (mailto:cib...@redhat.com) > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen
