Re: [mpc-dev] New features for Eclipse Marketplace and the Eclipse Marke

["Konstantin Komissarchik" <konstantin.komissarchik@xxxxxxxxxx>]

Any thoughts on these questions from last week? We are hoping to clean up Oracle marketplace entries in time for M7, but we are running into some issues.

 

I have created a new multi-variant “GlassFish Tools” entry and have marked existing “GlassFish Tools for X” entries as being “previous to Juno” to keep them out of the way of this test. Then I tried installing from different Eclipse versions. Mars M6, Luna and Kepler worked as expected. Juno displayed all entries, including “GlassFish Tools for X” that it shouldn’t be seeing. When I selected the multi-variant “GlassFish Tools” entry, it didn’t know what to do with it and selected the Mars variant.

 

Is Juno expected to work? What is the behavior expectations for Indigo and Helios?

 

A prompt response will help us in quickly moving Oracle marketplace entries to the new system.

 

Thanks,

 

- Konstantin

 

From: Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx]
Sent: Friday, May 01, 2015 9:12 AM
To: 'Communication between MPC committers'
Subject: RE: [mpc-dev] New features for Eclipse Marketplace and the Eclipse Marketplace Client

 

Thanks for the first set of answers. More questions/comments:

 

1. I see that versions prior to Juno are only supported as a single bucket (previous to juno - <= 4.1). Is there a technical reason that this couldn’t be implemented? We have Indigo and Helios variants of our solutions. It sounds like I’d either have to keep the “for Indigo” and “for Helios” as separate solutions or drop support for those platforms through Marketplace.

 

2. It seems that there is a bug. If multiple solution versions are specified, the additional details summary block seems to only list only one eclipse version. From the first one?

 

Thanks,

 

- Konstantin

 

 

From: Konstantin Komissarchik [mailto:konstantin.komissarchik@xxxxxxxxxx]
Sent: Thursday, April 30, 2015 12:06 PM
To: 'Communication between MPC committers'
Subject: RE: [mpc-dev] New features for Eclipse Marketplace and the Eclipse Marketplace Client

 

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

 

 

From: mpc-dev-bounces@xxxxxxxxxxx [mailto:mpc-dev-bounces@xxxxxxxxxxx] On Behalf Of Christopher Guindon
Sent: Thursday, April 30, 2015 10:42 AM
To: mpc-dev@xxxxxxxxxxx
Subject: [mpc-dev] New features for Eclipse Marketplace and the Eclipse Marketplace Client

 

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.

1. 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.
2. 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:

1. 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.
2. 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