Re: [eclipse.org-architecture-council] The "Eclipse Projects" Market

[Doug Schaefer <dschaefer@xxxxxxx>]

That’s a fair question. Most of the optional features are toolchain support. Until we get a new project wizard that doesn’t suck and confuse the hell out of new users, the sentiment of the committers is to keep them optional (e.g. Arduino C++). But a better new project wizard is on our roadmap and maybe something all projects can use (see the VisualStudio and Xcode wizards as examples). We’ll get there soon, just not in Mars.

Doug.

From: Wayne Beaton <wayne@xxxxxxxxxxx>
Organization: The Eclipse Foundation
Reply-To: Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Date: Friday, May 1, 2015 at 9:27 PM
To: Eclipse Architecture Council <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-architecture-council] The "Eclipse Projects" Market

Why aren't those features included?

At this point, the C/C++ solution in the market reflects the package features.

If there are other features that should be included, then shouldn't they be in the package?

Wayne

On 01/05/15 06:50 PM, Doug Schaefer wrote:

Maybe the C++ one is a better example. We have a tonne of optional
features for the CDT that aren¹t included in the C++ package. We need to
find a better way to present these to users and the Marketplace is a great
option.

Doug.

On 2015-05-01, 4:42 PM, "Marcel Bruch" <marcel.bruch@xxxxxxxxxxxxxx> wrote:

I¹ve no opinion or proposals yet but I¹ve some trouble to contrast this
approach with the existing EPP packages and (elsewhere discussed)
Oomph-based standard profiles.

More concrete:
Can you elaborate how, for instance, the Java Developer Tools Feature on
the Marketplace will be different to EPP Java package?
Bug 459905 sounds like this. Thus, I¹m missing the key motivation for
this step. I assume that you are looking for a greater flexibility than
we have today with EPP. Is this the main motivation?
Will EPP packages disappear some time soon?

Thanks,
Marcel
_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list, you
must contact emo@xxxxxxxxxxx to request removal.

_______________________________________________
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation