| Hi Konstantin, 
 The MP website will return the update site and
    
    installable units that matches the environment of the user:
 
 http://marketplace-staging.eclipse.org/content/test-entry-juno/api/p?os=win32&platform_version=4.2
 http://marketplace-staging.eclipse.org/content/test-entry-juno/api/p?os=win32&platform_version=4.1
 
 MPC will trow an error if you try to install a listing that's not
    compatible with your environment. That's a possibility if you try to
    install a listing with the drag and drop button from the MP website.
 
 We currently don't have any plans for migrating comments and likes
    but I can make it happen if you open a bug for this.
 
 The wiki page for the marketplace rest API was updated with more
    details:
 https://wiki.eclipse.org/Marketplace/REST#Compatibility_Filtering_.26_Multiple_Versions_per_Solution
 
 Cheers,
 
 
 On 2015-04-30 3:05 PM, Konstantin
      Komissarchik wrote:
 
      
      
      
      
        It’s
            great to see this improvement. Two questions:   1.
            How is backwards compatibility handled? If we have separate
            solutions right now for different Eclipse versions and we
            migrate to a single solution with multiple variants, what
            happens when a Luna or a Kepler client requests a listing?   2.
            Has there been any thinking on migrating comments and likes
            from existing solutions into the new merged solutions? It
            would be a shame to lose all of that with the transition.   Thanks,   -
            Konstantin       
          Dear Marketplace Listing Owners, We are very pleased to announce two new features for
            Eclipse Marketplace and the Eclipse Marketplace Client that
            will be part of the Mars release. 
            The Eclipse Marketplace Client has been
              improved to only display listings that are compatible with
              the version of Eclipse the user is running. As a
              Marketplace listing owner, you now have the ability to
              create different versions of your listings, called
              'Solution Versions', that are specific to the version of
              Eclipse. For each Solution Version, you can specify an
              update site, feature IDs, supported operating system and
              supported version of Eclipse. The default for all listings
              will be they are supported for all versions of Eclipse.For your Marketplace listing, you can now
              specify if a Feature ID is one of three conditions: 1)
              Required, 2) Optional but selected by default, and 3)
              Optional and not selected. We hope this will provide more
              flexibility for you to specify the feature IDs that are
              installed with Marketplace Client. Both of these features will be available in the Eclipse
            Mars release in June 2015. To prepare for Mars and these new
            features we recommend the following: 
            If your Eclipse listing is compatible with
              all versions of Eclipse then you don't need to do anything
              but we recommend you to have a look at your listing's
              feature IDs and specify which are required or optional.If your Eclipse listing is specific to a
              version of Eclipse, please create a new Solution Version
              in Eclipse Marketplace for each version. You can do this
              today from your Eclipse Marketplace account. Please let us know if you have any questions. 
 Regards,
 Christopher Guindon
 --  Christopher Guindon Senior Web Developer Eclipse Foundation Twitter: @chrisguindon 
 
 _______________________________________________
mpc-dev mailing list
mpc-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mpc-dev 
 -- 
Christopher Guindon
Senior Web Developer
Eclipse Foundation
Twitter: @chrisguindon |