| Summary: | Editor for p2.inf | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | curtis.windatt.public, gregory.amerson, heiko.boettger, irbull, jeffmcaffer, Lars.Vogel, lorenzo.bettini, mistria, pascal, torkildr, udo.hafermann |
| Version: | 3.7 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=401960 | ||
| Whiteboard: | |||
|
Description
Lars Vogel
Not sure about a wizard. But it certainly would be helpful to have an editor. Especially when setting up dependencies. I like the idea of an idea for p2.inf. I changed the title for this bug report. PDE does not plan on supporting an editor for a p2 file. I assume that Pascal moved this to PDE because p2 has no interest in supporting such an editor either. This will only be considered if someone steps up to create the editor and provide ongoing support. This editor could be a nice Google Summer of Code proposal... I wonder if the answer is an editor for the p2.inf file, or better support in our existing editors for the type of things we use the p2.inf file for. The p2.inf file is meant to be a 'low level' way to influence the publisher. In many cases (say negation requirements), it would be better to extend the feature.xml editor to provide a way to specify these things. Given a resource allocation choice, should we add p2.inf tooling, or should we improve our existing PDE/UI for these cases? (Yes I realize 'both' is the answer we all want to say) :-) People will probably always prefer feature.xml over p2.inf. So indeed the p2.inf is more a file that you add to a feature.xml to perform some hacks. It would be nice to have a dedicated p2.inf editor tab on the feature.xml or category.xml. For me the point of having a special p2.inf editor is easier editing of the file. It´s much better to hava an ui where you see whats possible and not having in outdated and incomplete documentation inorder to find a property that can be set when creating an installation unit. Also its likely that when doing copy paste modify to copy a property within an installation unit to forget updating the index. Marking as WONTFIX. Please reopen in case you intent to work on this. |