Those are all karaf provided features being used, so it seems like one of them is missing a wrap dependency or using something else that is missing the dependency.I also meant to mention, if it is just a missing transitive feature dependency, why isn't it just doing a standard feature validation failure saying wrap is required, instead of throwing an unsupported operation exception because it's trying to "uninstall" the wrap feature?Lifecycle Module Builder.build Project(Lifecycle Module Builder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded. Native Method Accessor Impl.invoke0(Native Method) at sun.reflect.Single Threaded Builder.build(Single Threaded Builder.java:51) at org.apache.maven.lifecycle.internal. Native Method Accessor Impl.invoke(Native Method Accessor Impl.java:62) at sun.reflect.The attribute must be entirely alphabetic characters.The attribute may have alpha-numeric characters, as well as dashes and underscores.
The attribute must have a value greater than or equal than the rule. The attribute must not have a value equal the rule. The attribute must be a valid date after the one passed on the rule.The example feature doesn't have a direct dependency on wrap, so it shouldn't have to declare a dependency on it.Shouldn't the feature (transitive) that's actually using wrap declare that dependency?The build works but there is an issue with verification so I am just not verifying any features that depend on the aardvarkhttpbundles feature.It will verify features after they if they do not have any http dependencies but will not verify features that do. It will not verify if you add it in the pom verification section. You will not be able to check the aardvark stuff but you should be able to reproduce the error by trying to verify jax-rs-connector.Mojo Execution Exception: Feature resolution failed for [aardvarkjaxrsbundles/1.0.0] Message: null Repositories: Resources: at org.apache.karaf.tooling.