What’s wrong with more discussion? Our packaging and distribution story still needs more work. From marketing perspective, offering a multitude of slightly-different options that users have trouble telling apart is well documented to cause confusion. The stats support this assertion. We can argue over the severity of the impact of this confusion, but it’s hard to argue that there is no confusion.
> As for the name ‘Eclipse IDE for Eclipse Developers’ can someone please explain what is an Eclipse developer?
I tend to agree that “Eclipse developer” term is ambiguous. It doesn’t only mean developers working on Eclipse. I think “Plugin Developer might be more clear in that respect.
- Konstantin
From: epp-dev-bounces@xxxxxxxxxxx [mailto:epp-dev-bounces@xxxxxxxxxxx] On Behalf Of Ian Skerrett
Sent: Monday, May 05, 2014 8:27 AM
To: 'Eclipse Packaging Project'
Subject: Re: [epp-dev] Java package
Do we really need to have yet another discussion on what is the correct package? It would be really nice if someone could point to a bug where someone expressed confusion with the current packaging strategy.
As for the name ‘Eclipse IDE for Eclipse Developers’ can someone please explain what is an Eclipse developer? The vast majority of people that visit our web site are Java developers.
As an Eclipse developer I want things like m2e available.
Doug, please open bugs for this. There is already one open to add Mylyn with Bugzilla, Gerrit and Hudson integration. Maven integration should be in there too.
“Eclipse IDE for Plugin Developers” and get rid of special placement “above the fold”?
I like "Eclipse IDE for Eclipse Developers" better. The package should include everything you need for developing Eclipse. However, I do think that’s an important signal that our top-offered package is the one for extending the Eclipse IDE. It’s shameless self-promotion but a really important driver (IMHO).