P2 Feature Generator merges Features
I've created a P2 Feature (with the P2 Feature Generator) after adding some more, PackageDrone began to merge the Features ~~randomly~~ as you can see on the pictures.
Origin Feature:

Generated Feature:

As you can see packagedrone merged the netty-Feature into my shell-Feature. Am I doing something wrong or is it a bug?
I noticed every generated Feature looks the same. Also the first generated Feature netty looks like the others. It seems to be only one generated Feature is deployed for every one.
Version: Package Drone 0.12.0.20151207-1732 (.deb-Package)
Right now the generated features do not support something like a "filter" which selects which bundles will be added to the feature. Each feature will contain all bundles and features of this channel.
I really would like to have something like a selector which allows to group and auto-create features.
But if this not working, as aspected. Whtat is the intended use of the create Feature functionality in this moment?
Well the intended use case was to combine all bundles and features into one feature. So that works as expected.
Of course over time you start to get more ideas, which you cannot always implement due to the lack of time.
Ahh okay, thanks for the reply.
For the person who is going to implementing this I'll will describe our usecases.
- We are creating Api-Bundles for defining the communication-interface. For every product (which has one or more api) we are creating one feature which cotains all necessary Api-Bundles for that product. We would like to have one channel, we call it 'common-model', where you can find any feature for a product, so you know how to communicate with the api.
- Every product is structured in the same way and need nearly the same third-party dependencies. So we started to create a shell-feature which contain every dependency for using the console in eclipse and we created a feature which contains all depencies for providing a REST-api and so on .... It would be nice if we could provide all these features in the same channel for example 'thirdparty features'
As Workaround we are creating a channel for every feature we want to have.
This is our usecase :D of course there a lot of different other examples. But I hope this will help to get an image how it could/should work.