DEADLOCK launching tomorrow night for FREE!!!
Posted 6 years ago
Yes – thats right – our competitive online shooter,
Deadlock is launching tomorrow night – 11pm in the US
– for FREE!!!!!
Latest Games
Action, Adventure
Featured Titles
Crescent Moon ClassicsWith the calculated release version, the release can be determined from the following mapping:
4.5.x.xxx (Mars)
4.4.x.xxx (Luna)
4.3.x.xxx (Kepler)
4.2.x.xxx (Juno)
3.8.x.xxx (Eclipse 3.8 - parallel release to Juno)
3.7.x.xxx (Indigo)
3.6.x.xxx (Helios)
If the calculated release version cannot be matched to an Eclipse release, no filtering will be performed.
Here are some example queries for the different versions as their corresponding MPC version would generate:
This will return a listing of all catalogs that are browsable with the MPC. It also includes basic branding parameters, like title and icon and strategies resolving dependencies. If you want to override this url (e.g. in your RCP application) you have to set the following system-property:
-Dorg.eclipse.epp.internal.mpc.core.service.DefaultCatalogService.url=
This setting will request the url
to obtain all available catalogs.
XML example
&marketplace&
&catalogs&
&catalog id="38413" title="Eclipse Marketplace" url="" selfContained="0" icon=""&
&description&Eclipse Marketplace (MP) is a place to find and keep track of Eclipse-based solutions.&/description&
&dependenciesRepository&&/dependenciesRepository&
&wizard title=""&
&icon&&/icon&
&searchtab enabled="1"&Search&/searchtab&
&populartab enabled="1"&Popular&/populartab&
&recenttab enabled="1"&Recent&/recenttab&
&news shorttitle="January 01/27" timestamp=""&&/news&
&/catalog&
&/marketplace&
marketplace
(@attribute) id: [int] Unique identifier
(@attribute) title: [string] Name of catalog
(@attribute) url: [string] Url prefix of the marketplace catalog
(@attribute) selfContained: [bool] TRUE/FALSE
(@attribute) icon: [string] Absolute url
description: [string] Short description
dependenciesRepository: [string]
(@attribute) title: [string] Title of Wizard
icon: [string] Absolute url
searchtab: [string] Search tab title
(@attribute) enabled: [bool] TRUE/FALSE
populartab: [string] Popular tab title
(@attribute) enabled: [bool] TRUE/FALSE
recenttab: [string] Recent tab title
(@attribute) enabled: [bool] TRUE/FALSE
news: [string] News content URL.
(@attribute) enabled: [bool] TRUE/FALSE
This will return a listing of Markets and Categories, it includes URLs for each category, as well number of listings in each category.
XML example
&marketplace&
&market name="Tools" id="31" url=""&
&category id="1964" count="158" url="" name="Application Development Frameworks" /&
&market name="Long Term Support" id="3429" url="" /&
&/marketplace&
marketplace
(@attribute) name: [string] Title
(@attribute) id: [int] Unique identifier
(@attribute) url: [string] Url
category (optional)
(@attribute) id: [int] Unique identifier
(@attribute) count: [int] Listing count
(@attribute) url: [string] Url
(@attribute) name: [string] Title
http://markerplace.eclipse.org/taxonomy/term/[category id],[market id]/api/p
This call returns a set of listings that correspond to the category / market specified.
Example: If you wanted to return the XML for all Build and Deploy Listings in the Tools Market you would use this call.
These urls are easily obtained from using the
XML example
&marketplace&
&category id="4" marketid="31" name="Build and Deploy" url=""&
&node id="69" name="MyEclipse Enterprise Workbench" url=""&
&favorited&34&/favorited&
&installstotal&5394&/installstotal&
&installsrecent&0&/installsrecent&
&/category&
&/marketplace&
marketplace
(@attribute) id: [int] Unique identifier
(@attribute) marketid: [int] Unique identifier
(@attribute) name: [string] Title
(@attribute) url: [string] Url
(@attribute) id: [int] Unique identifier
(@attribute) name: [string] Listing Title
(@attribute) url: [string] Listing Url
favorited: [int] Number of times a listing was favorited
installstotal: [int] Install count
installsrecent: [int] Install count for the last month
There are two methods of returning a specific listing.
http://marketplace.eclipse.org/content/[title]/api/p
http://marketplace.eclipse.org/node/[node id]/api/p
Calls to either URL will return a listing of contents of a node.
XML example
&marketplace&
&node id="29591" name="JRebel for Eclipse" url=""&
&type&resource&/type&
&categories&
&category id="4" name="Build and Deploy" url="" /&
&category id="24" name="IDE" url="" /&
&category id="9" name="J2EE Development Platform" url="" /&
&category id="17" name="Tools" url="" /&
&category id="20" name="Web" url="" /&
&/categories&
&tag id="134" name="J2EE" url="" /&
&tag id="327" name="eclipse" url="" /&
&tag id="422" name="java ee" url="" /&
&tag id="573" name="tools" url="" /&
&tag id="614" name="productivity" url="" /&
&owner&Oliver White&/owner&
&favorited&66&/favorited&
&installstotal&0&/installstotal&
&installsrecent&140372&/installsrecent&
&shortdescription&SHORT DESCRIPTION&/shortdescription&
&body&LONG DESCRIPTION&/body&
&created&&/created&
&changed&&/changed&
&foundationmember&1&/foundationmember&
&homepageurl&&/homepageurl&
&image&&/image&
&license&Commercial&/license&
&companyname&ZeroTurnaround&/companyname&
&status&Mature&/status&
&supporturl&&/supporturl&
&version /&
&eclipseversion&4.5, 4.4, 4.3, 4.2, 4.1&/eclipseversion&
&updateurl&&/updateurl&
&iu selected="TRUE"&org.zeroturnaround.eclipse.feature&/iu&
&iu selected="TRUE"&org.zeroturnaround.eclipse.wtp.feature&/iu&
&iu selected="TRUE"&org.zeroturnaround.eclipse.m2e.feature&/iu&
&platforms&
&platform&Windows&/platform&
&platform&Mac&/platform&
&platform&Linux/GTK&/platform&
&/platforms&
&/marketplace&
marketplace
(@attribute) id: [int] Unique identifier
(@attribute) name: [string] Listing Title
(@attribute) url: [string] Listing Url
type: [string] This is the type of listing being returned. 'training' is for a Training and Consulting Listing, 'resource' is for a solutions listing.
categories
(@attribute) id: [int] Unique identifier
(@attribute) name: [string] Title
(@attribute) url: [string] Url
(@attribute) id: [int] Unique identifier
(@attribute) name: [string] Title
(@attribute) url: [string] Url
owner: [string] Name of the author
favorited: [int] Number of times a listing was favorited
installstotal: [int] Install count
installsrecent: [int] Install count for the last month
shortdescription: [string] Listing teaser
body: [sting] Full description
created: [int] Timestamp
changed: [int] Timestamp
foundationmember: [bool] TRUE/FALSE
homepageurl: [string] Listing URL website
image: [string] Logo absolute URL
license: [string] Listing license
companyname: [string] Company name
status: [string] Release status
supporturl: [string] Support/documentation URL
version: [string] Version name
eclipseversion: [float] Eclipse release number (4.5, 4.4...)
updateurl: [string] Update site URL
ius: Feature ID's are used by the Eclipse Marketplace Client (MPC) to determine which features to install for your listing
(@attribute) required: [string] TRUE or FALSE
(@attribute) selected: [string] TRUE or FALSE
platform: [string] Compatible OS (Windows, Mac, Linux/GTK)
will return a Training and Consulting Listing
will return a Solutions Listing.
http://marketplace.eclipse.org/api/p/search/apachesolr_search/[query]?page_num=[page num]&filters=[filters]
There is one exception to using the api/p at the end of URLs. The search API needs this string to be at the start of the URL.
query: This is the string you wish to query the database with
page num: The search API returns 10 results per page. Use this parameter to iterate though pages. The root node will always return the total number of results.
filters: There are 3 different filters used by the Apache Solr search database that can be used to constrain (Facet) your searches. If you plan to use more then one filter they must be SPACE separated.
tid: This field is the database equivalent of category IDs.
tid:31 This query would search for 'Enterprise' in the J2EE category of the Tools Market.
sm_field_status: this filter is the equivalent of the &status& tag in a listings XML result.
This query would search for 'Enterprise' listings that have a Status matching 'Production/Stable'
sm_field_licensetype: this filter is the equivalent of the &license& tag in the listings XML result.
EPL' This query would search for 'Enterprise' listings that have a License Type matching "Free EPL".
XML example
&marketplace&
&search term="test" url="" count="1"&
&node&&/node&
&/marketplace&
marketplace
(@attribute) term: [string] Search keyword
(@attribute) url: [string] Url
(@attribute) count: [int] Result count
This call will return a list of Featured Listings. By default this returns 6 listings. The default is configured on the server.
If available, it can insert up-to two promoted downloads at the top of the list. It is possible to see a commercial listing here.
This call will return a list of featured listings constrained by a category / market id (or both). By default this returns 6 listings. The default is configured on the server.
- This call will return featured items from the Code Management (ID = 2) Category.
- This call will return featured items from the Tools (ID = 31) Market.
- This call will return featured items that are contained in both the Code Management and Tools categories.
XML example
&marketplace&
&featured count="10"&
&node&&/node&
&/featured&
&/marketplace&
marketplace
(@attribute) count: [int] Result count
This call will return a list of Recently Updated or Added Listings.
By default this returns 6 listings.
The default is configured on the server.
XML example
&marketplace&
&recent count="10"&
&node&&/node&
&/marketplace&
marketplace
(@attribute) count: [int] Result count
This call will return a list of the Most Favorited Listings.
By default this returns 6 listings.
The default is configured on the server.
XML example
&marketplace&
&favorites count="10"&
&node&&/node&
&/favorites&
&/marketplace&
marketplace
(@attribute) count: [int] Result count
This call will return a list of Most Popular listing by activity.
By default this returns 6 listings.
The default is configured on the server.
XML example
&marketplace&
&popular count="10"&
&node&&/node&
&/marketplace&
marketplace
(@attribute) count: [int] Result count
This call will return a list of entries related to what's already installed in the running Eclipse. Installed entries are sent to the server as node ids in an additional query parameter
nodes: A list of space-separated node ids for installed marketplace nodes, url-encoded.
This feature is already supported by the MPC client through a 'Related' tab that needs to be enabled in the catalog's branding information, see . The server at marketplace.eclipse.org does not yet support this query at the moment, see .
A catalog is an HTTP service which returns XML data back to the Marketplace Client from.
Currently Marketplace uses PHP with an SQL backend to serve these pages to the MPC.
In terms of building your own catalog with this data you would follow a three step process.
Query the Base URL for a listing of Markets and their categories.
Iterate through that query to retrieve listings for each category using the Category URL.
Finally iterate through the Category Query to retrieve the data related to each node.
Catalogs are managed through a registry on marketplace.eclipse.org. Each catalog is listed with its REST URL and branding information (Title, catalog icon, MPC wizard icon, supported MPC tabs).
A list of catalogs can be retrieved from
XML Example
&marketplace&
&catalogs&
&catalog id="38413" title="Eclipse Marketplace" url="" selfContained="0"
&description&
Eclipse Marketplace (MP) is a place to find and keep track of Eclipse-based solutions.
&/description&
&dependenciesRepository/&
&wizard title=""&
&icon&&/icon&
&searchtab enabled="1"&Search&/searchtab&
&featuredmarkettab enabled="1"&Eclipse Project&/featuredmarkettab&
&populartab enabled="1"&Popular&/populartab&
&recenttab enabled="1"&Recent&/recenttab&
&relatedtab enabled="1"&Related&/relatedtab&
&news shorttitle="March 05/26" timestamp=""&&/news&
&/catalog&
&/catalogs&
&/marketplace&
Since MPC Kepler, it's possible to add an additional tab containing an embedded browser component that shows a news page. The page URL to display will be included in the marketplace catalog description pulled from the server. It's possible to override a catalog default URL with news/api/p.
Here's an example of the default Eclipse Marketplace catalog news page:
(MPC) project implements a client to the REST API.
The client provides public Java API for accessing the REST API in the org.eclipse.epp.mpc.core plug-in through the classes in the org.eclipse.epp.mpc.core.service package.
Of interest to clients to the REST API:
IMarketplaceServiceLocator is an OSGi service that can be used as an entry point to access the catalog service and specific marketplace services.
IMarketplaceService gives access to the marketplace REST API
ICatalogService gives access to the catalog registry
The marketplace data model is available through interfaces in the org.eclipse.epp.mpc.model package.
In addition to the Java REST API, there is also some API to access the Marketplace Client wizard dialog in the org.eclipse.epp.mpc.ui plug-in:
MarketplaceClient offers some simple helper methods to open a wizard and to give access to the more elaborate IMarketplaceClientService
IMarketplaceClientService offers more elaborate configuration options to open a wizard in a specific state, e.g. with specific markets, entries preselected for install, or directly on the installation page.
Furthermore, of interest to catalog providers or implementors of client libraries to access the REST API in MPC:
/org.eclipse.epp.mpc.core/mpc-rest.xsd An XML Schema that describes the REST API data format
org.eclipse.epp.internal.mpc.core.service.DefaultMarketplaceService A Java class that provides a Java API to the REST service
org.eclipse.epp.mpc.tests.service.DefaultMarketplaceServiceTest A JUnit test case that exercises the REST API