Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pde-dev] p2 metadata authoring proposal

+1

Integrating PDE and p2 in a way that best helps users is a priority for 3.5. We will definitely need good communication between the interested parties. A wiki page describing the design would be helpful.

My biggest concern is that this will just end up being another tool in PDE that only some users can/will use. We already have the feature editor, site editor, target editor, product editor, and projects to go with them. Just adding an IU editor/project adds more confusion for users and more code to maintain. If the work can simplify work in PDE, awesome, if not, it needs to at least be a light weight solution, so no new projects :)

Curtis


Inactive hide details for Henrik Lindberg ---05/28/2008 07:51:21 AM---Hi, I am very interested in p2 metadata authoring and wouHenrik Lindberg ---05/28/2008 07:51:21 AM---Hi, I am very interested in p2 metadata authoring and would like to contribute.


From:

Henrik Lindberg <henrik.lindberg@xxxxxxxxxxxxxx>

To:

pde-dev@xxxxxxxxxxx

Date:

05/28/2008 07:51 AM

Subject:

[pde-dev] p2 metadata authoring proposal




Hi, I am very interested in p2 metadata authoring and would like to contribute.
I have opened an issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=233672
Jeff McAffer suggested that I write this proposal to outline the work, and that an PDE incubator work area should be set up for this project.

(Disclaimer: As I am learning more about p2 every day so some of the things I describe here may be a bit "off")

The problems this project should solve:
- Several types are "adapted" to installable units by p2 (e.g. features and plugins), but there is no direct authoring available.
- Existing "adapted" installable units may have meta data that needs to be modified/augmented in order for the unit to be useful - there is a mechanism available to provide advice to the resolution mechanism, but authoring of such advice is not.

I think the work consists of:
- A wiki page (or several) describing "design of metadata authoring"
- An XML definition for "authored installable unit" (a candidate is the <unit> format in the local meta data repository). It should be possible to create such an "iu" file with any name without requirements that it is in some special project or folder.
- An XML definition for "advice to adapted installable unit" (as I am not sure what is needed here).
- An editor for Installable Unit
- An editor for Installable Unit advice (is perhaps the same editor).
- A way to test the installable unit (resolution, install-ability)
- A way to export/publish installable units
- Settings/preferences

I have some question regarding best way to collaborate. Which mailing list to use for design discussions? Or if discussion should be in the bugzilla issue? Is it a good idea to have a wiki page to describe the "latest design"?

Regards
Henrik Lindberg
henrik.lindberg@xxxxxxxxxxxxxx


_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev

GIF image

GIF image


Back to the top