Hi Guillame, Firstly, thanks for looking into this. In regard to the "overuse of the prerequisite flag", keep in mind that the project I checked in is completely artificial. Before checking in the project, I removed many references to bundles that are not in the public maven central repository from the feature definitions so that you could reproduce the issue.
However, it is possible that I am still overusing the prerequisite flag, and in that case can you please explain to me what the objective criteria are for using the prerequisite flag? I assumed that if a feature has bundles which depend on bundles provided by another feature then I should use the prerequisite flag. For example, camel needs jline and jline is provided by the shell feature so why shouldn't camel mention "shell" as a prerequisite? Alternatively, can you show exactly where in the project there are redundant uses of the prerequisite flag and explain why it is redundant so that I don't make the same mistake again? -- View this message in context: http://karaf.922171.n3.nabble.com/Features-Core-bundle-stuck-in-Resolved-state-tp4047964p4047998.html Sent from the Karaf - User mailing list archive at Nabble.com.
