Hi,

just recently I stumbled over a strange effect while building a customized
Karaf with boot features.
In the end it turned out, the reason for that had been two features with
the same name but not the same content.

Right now we do have a jpa feature in the enterprise repository
(feature.xml) in version 2.6.0
While the same feature name exists from the aries repository (feature.xml)
also in version 2.6.0

I opened an issue for this:
https://issues.apache.org/jira/browse/KARAF-5185
right now I'm in favor of dumping the jpa feature in the enterprise
repository in favor of the aries jpa feature. If there are no objections
I'd start to remove the enterprise feature.

In general though we can't really expect to have unique feature names only
by the feature name itself. Maybe it's time to take the repository also
into account as coordinate for feature declarations?

regards, Achim

-- 

Apache Member
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS>

Software Architect / Project Manager / Scrum Master

Reply via email to