Details
Major Description
When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.