I saw camel in your previous list and that requires aries-blueprint but doesnt have it listed as a dependency. I made sure blueprint was loaded first by putting in paranthasis
(aries-blueprint), wrap ... This might be the issue you are having. It is one I had. On 2015-10-05 12:30, xlogger wrote: > Hi JB, > > Thanks for your reply. I just found an older thread also discussed about > this > http://karaf.922171.n3.nabble.com/Karaf-Custom-Distribution-Could-not-find-matching-feature-for-standard-td4039832.html > [1] > > I tried to follow your reply on Apr 21 and add the list of features like > shell, jaas, aries-blueprint... etc to bootfeature... although the mvn build > can be success, there are always error logs complaining about missing > dependent bundles or features when I startup my custom karaf > > P.S. I perform mvn build in connected env and startup my custom karaf in > closed env without internet and all external mvn links > > meta-features like "standard" with all dependency issue resolved during > karaf-assembly mvn build definitely helps. Looking forward to that. > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Standard-feature-as-boot-feature-for-custom-distribution-tp4042884p4042892.html > [2] > Sent from the Karaf - User mailing list archive at Nabble.com. Links: ------ [1] http://karaf.922171.n3.nabble.com/Karaf-Custom-Distribution-Could-not-find-matching-feature-for-standard-td4039832.html [2] http://karaf.922171.n3.nabble.com/Karaf-4-0-1-Standard-feature-as-boot-feature-for-custom-distribution-tp4042884p4042892.html
