Message Title

I'm including the feature file provided by hibernate in a custom feature which looks something like this:

<features xmlns="http://karaf.apache.org/xmlns/features/v1.2.0" name="somefeature">
	<repository>mvn:org.hibernate/hibernate-osgi/${hibernate.version}/xml/karaf</repository>
	
	<feature name="dependencies" version="1.0.0">
		<feature>jdbc</feature>
        	<feature version="3.0.4">jndi</feature>
	        <feature version="1.1.1">transaction</feature>
        	<feature version="2.1.0">jpa</feature>
		<bundle>mvn:mysql/mysql-connector-java/${mysql-connector-java.version}</bundle>
		<bundle>mvn:com.zaxxer/HikariCP/${HikariCP.version}</bundle>
		<feature version="${hibernate.version}">hibernate-envers</feature>
	</feature>
	
	<feature name="configuration" version="1.0.0">
		<!-- some propertie files -->
	</feature>
	
	<feature name="application" version="1.0.0">
		<feature>configuration</feature>
		<feature>dependencies</feature>
		<!-- rest of the application, including persistenceUnit -->
	</feature>
	
</features>

Adding this feature file to karaf and installing the feature "application" leads to the exception above.
Just installing the feature "dependencies" works.

I looked in hibernate-envers bundle manifest and it seems, that there are no dependencies (neither package nor capability) to hibernate-entitiymanager. So my assumption is, that the the feature resolver tries to start envers before entitymanager.

A proper fix would be do add a dependency, not setting the start-level (which is removed in karaf 4 anyways).