Eclipse Marketplace & the future(tm)
Over at the Eclipse Marketplace we’ve made some improvements to the site, that I'd like to bring your attention to.
Free Tagging
The first big change you may notice is that we’ve added the ability for anyone to specify their own tags on any listing. You can find the free tagging interface on your listings pages. Feel free to tag your listings with your own tags or ones that have already been used.
The Marketplace Client
So you're working in Eclipse and realize that you need plug-in to do X. Wouldn't it be great to load up a plug-in browser right in Eclipse?
We’ve recently announced the creation of a new project at Eclipse called the Marketplace Client Project (MPC), which will allow users to browse and install listings on Marketplace directly from their Eclipse installation. In order to prepare for this client to launch we’ve added two new fields to the Marketplace solutions listings.
Installable Units
The first new field that we’ve added is to allow you to add a listing of Installable Units for your product. The installable units you provide will need to appear in your content.jar files located on your p2 repository site.
Platforms
The second field that we’ve added is to allow you to specify the platforms your products support. This field will be used to filter out listings that would not otherwise be able to install on the target platform.
Screenshots
You may also notice that when editing your listing there is a new field to provide a screenshot. In the near future we’ll be adding a tab to your listings to display the screenshots.
posted by Nathan at 10:18 AM
2 Comments:
Just out of curiosity, why are the new fields necessary? Why can't the plugin just use P2 to read the repository for the supplied features?
1:41 PM
We're aiming for a 1-Click install with the Client.
Take for instance a plugin like Subclipse, it's not just one installable units. When you put in that p2 location to your Eclipse there's a multitude of things to install. Sure you want Subclipse, but what about SVNKit Implementation, Collabnet and Mylyn Connectors etc. Most users won't want these installed by default.
As for Platforms this is done to assist filtering of the data when your browsing the client. We also don't want the client being chatty. If you search for certain items we don't want the client to connect via p2 for every result returned to determine if you'll even be able to install it.
4:09 PM
Post a Comment
<< Home