What is the eclipse plugin update release mechanism? - eclipse

I want to emulate the eclipse update mechanism in my custom Eclipse RCP Application. So, I want to konw that If Eclipse team updates one plug-in, what they will they do for:
the version of this plug-in;
the version of the feature which include this plug-in;( maybe there are so many features ) ;
the version of the feature which include the feature above;( maybe there are so many features ) ;
I care more about the features, they will all be rebuild ?
If anyone knows this, can give me some advice, thanks a lot!

Related

How to develop something as a group in Eclipse

My friend and I were searching for already built-in features in Eclipse or plugins that allow you to develop code in a group, or to be more specific, in a pair.
I found only a single plugin that provides such features, however it is quite hard to install.
Are there any simple solutions for Eclipse, or should I use a different editor?
You could use Git/GitHub or a similar form of version control. I am pretty sure Eclipse has built in support for Git.

Eclipse - New Project

I need to modify project creation in eclipse. I would like to add my own project creation. For example, when developer selectes File->New->Project, I want my option (i.e, XYZ Java Project) under to be available. Is this possible ? If yes, i am looking for some direction to begin with ?
Thanks.
To begin with you need to contribute your own Eclipse Plug in. Download Eclipse plugin developers IDE from this Location.
You can contribute a Custom Project Wizard through Extensions.
Define your Project Nature
For reference you can check this example Create a Custom Project in Eclipse – New Project Wizard: the Behavior
Hope this helps !!
Yes you can. A robust way to do this is to make an eclipse plugin so that it gets added to the menu. I was just looking into this myself a couple of days ago and this is what I found.
Here are some links:
O'Reilly
Better yet though, let me just show you an answer about this: https://stackoverflow.com/a/299316/879485
If you use Maven you can have a look at archetypes. Maven also has the ability to create Eclipse projects. With this you should have all the tools necessary to automate whatever project layout you need to have.

Creating a language extension for Eclipse?

Is it possible to create an extension or plugin for Eclipse that gives support to a specific language? Where i can find information about that? Also, can i repackage Eclipse, along with that plugin, and distribute the new package, just like PDT, for example?
Have a look at this page:
http://wiki.eclipse.org/The_Official_Eclipse_FAQs
There is a section "Implementing Support for Your Own Language" at the bottom of that page.
You should definitely have a look at Xtext which allows you quite easily to get first grade ide support for your own langage.
http://www.eclipse.org/Xtext/
It's possible. In fact support for specific languages is implemented as plug-ins. See eclipse platform plug-in developers guide and then search for details. Or look for some book like eclipse plugins.
You can repackage and distribute new package. In fact eclipse license gives you more freedom in this than for example GPL.

Which Eclipse package for total noob to download, and can I change it later?

Many different Eclipse packages are listed on http://www.eclipse.org/downloads/ and the comparison chart on http://www.eclipse.org/downloads/compare.php helps with knowing some of the differences. What I don't know as a total Eclipse (and Java) noob is how important it is to download the "right one" and how easy it is to fix things afterward if I discover I need some feature/capability/addon/whatever later.
For example, I need to get up to speed on RCP (whatever that is) quickly, but suspect I might want to also know about "EMF" and "GEF" and other things which aren't in the RCP version of Eclipse, or not listed at all such as SWT. I'm further confused by the top line of the comparison table, "RCP/Platform" with checkmarks under all columns - does this mean any package will do for learning the basics of RCP? This is not noob-friendly!
As an Eclipse know-nothing, what should I do?
I'd say download Eclipse Classic, then you can add whatever you need as plugins when you discover you need them in the future.

Which one is better (in support, difficulty, ...) to develop a plugin, Netbeans or Eclipse?

I would like to make a new plugin for a programming language because there is not any IDE the time I asked this question. I think IDE developing is far more easier if I try to use one of the available platform like Netbeans or Eclipse or ...
As I checked, Eclipse plugin (if that plugin is not updated) won't be able to start up after 1 or 2 years. I mean, Eclipse develops a way that old plugins has to follow in order to hold the compatibility.
I can't answer your original question as I have not developed for Netbeans.
As the backwards compatibility, if the version dependencies are set right, and only the API from other plug-ins are used, the old plug-in should work (there are some exceptions, but in that case upgrading the plug-in does not take too much effort, as there is documentation about what has changed).
The main drawback in Eclipse development is that documentation is sometimes scarce, but for common tasks there is some available.
Sorry, I also can answer only 1/2 of your question.
I have developed (small) eclipse plugins and an eclipse RCP. Both were a breeze. I agree with #Zoltan's comment, get your dependencies right & don't use some back-door unsupported feature in aplugin you don't control & your problems should be minimal. Even if you did run into a dependency problem, the configuration is straightforward enough that you could make an updated release of your plugin very quickly.