| Prerequisites with wildcards in Cspec/x [message #510526] |
Wed, 27 January 2010 12:32 |
Eclipse User |
|
|
|
Hi all,
Looking at the generated Cspec for e.g. an eclipse feature project, there are many groups (and actions) that aggregate attributes of the
feature's dependencies by listing the attributes of all dependencies like this:
<cs:public name="bundle.jars">
<cs:attribute name="bundle.and.fragments" component="org.example.bundle1"/>
<cs:attribute name="bundle.and.fragments" component="org.example.bundle2"/>
<cs:attribute name="bundle.and.fragments" component="org.example.bundle3"/>
...
</cs:public>
This is fine for generated groups. It is, however, rather impractical for specifying similar groups manually in a Cspex, since they would
need to be adapted whenever the component's dependencies change.
It would be a lot nicer to be able to do something like this (to pick up the example above)
<cs:public name="bundle.jars">
<cs:attribute name="bundle.and.fragments" component="org.example.*" componentType="osgi.bundle"/>
</cs:public>
to express "a group of all attributes named bundle.and.fragments from all dependencies of type osgi.bundle matching org.example.* that have
an attribute of that name".
Does this seem feasible? Is there maybe already some other way to do this that I missed?
Regards,
Carsten
|
|
|
Powered by
FUDForum. Page generated in 0.05313 seconds
Home