Allow Creation of Features and Source Features about p2-maven-plugin

[tombujok]

Hi. Thanks for your comment. I do not really get what you mean though. Do I understand it correctly that you would like to generate a p2 site including jars that are not maven artifacts (eclipse feature, plugin)? Or do I get it wrong? The plugin is not supposed to support it. It is supposed to work on maven artifacts only.

[kingargyle]

Right now it uses a generic category. Xml to expose all bundles and
sources. However it would be nice to create a feature with just a few
exposed. Not sure how if you can read a feature.xml file and a category
file that includes the feature.

I can get around it with a two stage build but would be nice to just do it
in one.
On Oct 21, 2012 3:56 PM, "Tom Bujok" [email protected] wrote:

Hi. Thanks for your comment. I do not really get what you mean though. Do
I understand it correctly that you would like to generate a p2 site
including jars that are not maven artifacts (eclipse feature, plugin)? Or
do I get it wrong? The plugin is not supposed to support it. It is supposed
to work on maven artifacts only.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-9646804.

[tombujok]

Now I get it. It would not be a problem to read an external category.xml file to expose a custom category. Right now there is one generic category indeed. I was thinking to expose a category per dependency (so that it includes the dependency specified, all the transitive dependencies and their source bundles). What do you think about such a solution?

[kingargyle]

Some we need to be able to specifically specify all these particular plugin
should be installed together. So if we can specify a feature.xml file and
have that considered I think it would help.

I like your option as well but I think it already works that way. At least
if I view it in eclipse ui I can install the individual plugin through
there.
On Oct 26, 2012 3:26 AM, "Tom Bujok" [email protected] wrote:

Now I get it. It would not be a problem to read an external category.xml
file to expose a custom category. Right now there is one generic category
indeed. I was thinking to expose a category per dependency (so that it
includes the dependency specified, all the transitive dependencies and
their source bundles). What do you think about such a solution?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-9804771.

[fikovnik]

Could this be a bit more flexible? Like defining your own categories? Some guys they manually pack all the 3rd party plugins into something like:

• 3rd party plugins runtime
• 3rd party plugins sources
• 3rd party plugins SDK

[kingargyle]

Yep. However you want to accomplish it.
On Oct 28, 2012 10:49 AM, "Filip Krikava" [email protected] wrote:

Could this be a bit more flexible? Like defining your own categories? Some
guys they manually pack all the 3rd party plugins into something like:

• 3rd party plugins runtime

• 3rd party plugins sources

• 3rd party plugins SDK

  —
  Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-9846447.

[tombujok]

It does now cover all aspects of this issue, but you can specify an external category.xml file - this is already supported. In such a way the plugins can be flexibly grouped. Have a look at the manual.

[tombujok]

Set to won't fix...