Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] Java IDEs comparison


Everything I didn't comment means I agree fully with. Things like good content in packages, too many perspectives & views are very relevant arguments IMO.

On 09/09/2016 03:09 PM, Michael Scharf wrote:
With JetBrains products upgrading to a new version has been seamless
so far.
That's because you're using only/mostly JetBrains' plugins, not community ones.
It's the same as if you're using only Eclipse bundles from Simultaneous Release, those are the ones that are tested by the community to work together.
Finding extension wit Jetbrains is easy: there just one place to
search for them. Installing plugins is like clicking a checkbox on a
list. I have not had any problems installing or updating plugins with
Jetbrains IDEs.
Finding extension for Eclipse IDE is easy with Neon: just double-click on a .py file in your IDE, and you'll get suggested to install PyDev.
In Jetbrains IDEs it is very easy to exclude folders form being parsed.
I've not used those tools, but IIRC, in JDT it's right-click > Build Path > Remove from build path. We can qualify it as very easy. I don't know how it is for Python and JS right now.
However, a consistent approach would be to have such a generic "ignore source folder" command and have whateverDT plugins implementing it.
If you think it makes sense, please create a bug for Platform UI and we'll followup there, hopefully reaching a good agreement and a change for Oxygen.
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

Back to the top