[Bug 469867] Could there be an api to load IUs into a solution listing, or copy from one solution to another, or copy from one solution VERSION into another? Or could we just use a textarea for all the IUs?
Bugzilla Link | 469867 |
Status | NEW |
Importance | P3 normal |
Reported | Jun 10, 2015 12:46 EDT |
Modified | Feb 28, 2020 15:47 EDT |
Description
For a solution listing like JBoss Tools [1], where we have more than 30 features, manually loading those via the web is painful. Having to copy them manually from one solution to another, as we'll have to do when JBoss Tools 4.3.0 is released, is a further pain.
[1] https://marketplace.eclipse.org/content/jboss-tools-luna/edit
We plan to have a Beta-quality listing for JBoss Tools (Mars), which will at some point become Final. At that point, those IUs can be copied over into the listing currently called JBoss Tools (Luna), since we can now add multiple versions to the same listing. But with the current web UI, I will have to manually copy all those IUs from the Mars entry into the Luna one.
So, here's what I would love to see from a web API.
a) ability to upload a text file containing a list of IUs, one per line, and have to added to the list of IUs for a given solution / version
b) ability to copy IUs from an existing solution into a new solution (or an existing solution's new version)
c) ability to export a list of IUs for a given solution into a text file, one per line. Could do one file for all versions (with some sort of header to differentiate) or else one file per version (better for diffing the list of IUs).
Are any of those possible?
Hell, even switching from the current UI with all the text input and select boxes to a single would be way better, because then you wouldn't need to implement any file import/export or copying mechanism. A user could just do that themself using the textarea contents.
I would set it up to use comma separation to define the type of inclusion, such as:
org.jboss.tools.usage.feature,Required
org.jboss.tools.vpe.browsersim.feature,Optional-Selected
org.jboss.tools.vpe.feature,Optional-Selected
And if the suffix is omitted, the tool would just assume "Optional-Selected" as the default, and put those values into the textarea field for the user to see.
This would also make the UI way simpler, and obviate the need for the "Add New Feature ID" button, the need to reorder features, or anything around setting row weights -- people could just reorder content in the textarea field as they wanted. It would also make fixing bug 469862 super easy. :D