Export a Plug-In - eclipse

I made a plugin in eclipse IDE but is in raw (is not packaged), I want to upload it to a repository so that people can download and install it in your IDE. i.e. they can go to Help-> Install New Software, add a url and download my plug-in. To run my plug-in it uses a grammar made ​​using the xtext modeling tool(plug-in). I dont know if there are any problems if my plug-in have others plug-in dependencies. I searched what could do and I found something related to the creation of PCR products:
*What are the differences between plug-ins, features, and products in Eclipse RCP?
*http://www.coplec.org/1-creando-una-aplicaci%C3%B3n-rcp/07-april-2008
I'm not sure if this help me to do for what I want do. I really appreciate any information about it. Sorry my English i know that is not very good. Ty :)

You want to create an update site to deploy your plugin. Dependent plugins (like the xtext runtime) should normally not be packaged directly into your feature. If the user checks the "contact all update sites during installation to find dependencies", then your dependencies will be fetched directly from the eclipse servers instead.

Related

Need suggestions on which plugin to install from eclipse market?

I am developing a new plugin in eclipse. I need a plugin from internet (for eclipse, of course) which I can dissect and understand its implementation (by looking into plugin.xml etc.). It would help me create my own plugin.
I want your help in suggesting some plug-ins which I download and dissect, so that i can use that logic to make my own plugin?
I will now give an insight to my proposed plugin:::
My plugin would take in some input via a GUI interface from the user and then I should be able to convert all the user input into a text file and trigger a perl script. It sounds sloppy, but I am completely new to Eclipse and Plugins.
I just need some suggestions from you experts.
Thanks a lot!!!
If you download either the Eclipse Classic package or the Eclipse for RCP Developers package, they include source for Eclipse itself. You can use the Eclipse plugins themselves as examples.

Platform-specific dependency creeping into Eclipse plugin

I have implemented a graph editor with Eclipse EMF and GMF frameworks. After completing my project, I realized that this plugin shows dependencies (not explicitly added by me) on some OS-specific plugins.i.e:org.eclipse.ui.win32, org.eclipse.swt.win32.win32.x86. And whenever I have tried to bypass this dependency at my update site something went wrong with the installation process of the plugin.
As such it is impossible to run my plugin in *nix environment or even win64 machines.This seems a very heavy constraint dependency to me. Am I doing something in a wrong way? Or is there no other way of building Eclipse plugins which are cross-platform other than building the project from scratch at each different OSs?
We created a similar style of plug-in in my project. Under "Plug-in Dependencies" in Package Explorer I can see org.eclipse.swt.win32 listed, but it is not listed in required plug-ins in plugin.xml.
We also successfully created an update site which works for Mac users without issue.
So, yes it is possible to have a cross-platform plug-in.
I would suggest you first try to to use "Export..." -> "Deployable plug-ins and fragments" to create a bunch of jar files for your plug-in. See if these can be successfully installed by copying into the drop-ins folder of a fresh eclipse installation. Do this first on a Win32 install, then try on another platform. Once you have that working, use the new Eclipse installation to create the Update site.

Boostrapping new Eclipse machines with all the Plugins

Bootstrapping Eclipse on new machines is such a time consuming process, you wind up asking yourself whether you really need each plugin. But there all handy, and help develop consistent habits.
Eclipse bootstrapping problems include:
Explaining / documenting what needs to happen
The actual time pasting in the right URLs and downloading
Version compatibility and dependencies
Eclipse likes to restart after each one
The changeover to the Eclipse Marketplace means that some plugins and instructions you find on the web tend to be inconsistent, depending on when they were written.
The Licenses... over and over and over... yes, yes, yes... I understand that the person installing needs to be aware of it, and have a chance to review them, but there's got to be a better way.
It'd be nice to have "patch file" (either binary or meta) that spells out what I want to add on top of stock Eclipse installation. I'd really like to find (or create) a 1 or 2 step process that sets up Eclipse, plus a favorite batch of plugins:
subclipse
m2eclipse
jetty support like runjettyrun
android sdk and plugin (or at least just the plugin)
aspectj
Web Objects / WOLiops
python, other langs
JVM Monitor, maybe EclEmma
probably a git plugin pretty soon.
Does command line maven help with any of this? It seems like its repository management would fit at least part of the functionality.
On a machine with an Eclipse installation matching your needs use File -> Export -> Install -> Installed software items to file. Import the generated file using the same menu on all other machines.
As Scott says, a good approach is to simply package a fully prepared Eclipse installation once all the plugins you need are installed. The downside is that you have to update most plugins afterwards.
Another option is to use Yoxos. With it, you can create a profile and configure it with all the plugins you need (and apparently Yoxos can do more than that).
Finally, this page might interest you concerning the configuration side of things.
Solution 1 is too search for more advanced Eclipse distributions.
For example, STS (Spring Tool Suite) comes with
AspectJ
EGit
m2e
(and of course) Spring IDE
One small trick can be done with m2e-android - Android Configurator for M2E Maven Integration. If installing it on clean Eclipse, it will also automatically resolve to install :
m2e
Android Developer Tools (ADT)

How to disable Eclipse compiler

Is it possible to disable or remove the built-in Java compiler from an Eclipse installation?
I would like to use the XML editing and validation features of Eclipse in an environment that forbids installation of compilers. Can the compiler be disabled/removed without breaking the XML editing and validation functions? How?
Comments in this related question suggest that it can't be done, but I don't need the Java development features of Eclipse (and don't expect them to work without the compiler).
Yes, it is certainly possible to create an Eclipse install without the Java compiler (or JDT to be specific). The real question is whether the XML tools have an indirect dependency on JDT that will pull that back in.
Here is what I would try...
Download Eclipse Platform zip. You can get it from this URL:
http://download.eclipse.org/eclipse/downloads/
Look under the Latest Releases heading. You will want to download something stable. The latest release now is 3.6.1...
http://download.eclipse.org/eclipse/downloads/drops/R-3.6.1-201009090800/index.php
Now find a heading called "Platform Runtime Binary" and download the zip that's right for your platform. Verify that file name is "eclipse-platform-[version]-[platform].zip". If it isn't you've downloaded the wrong thing.
Unzip it as you usually would an Eclipse distro. You now have a runnable Eclipse install, minus any and all interesting IDE functionality. In particular, there is no JDT.
Now it's time to install XML tools. Go to Help->Install New Software->Add and use this URL for the repository: http://download.eclipse.org/releases/helios/
Uncheck "contact all update sites during install to find required software".
Type in XML into the filter field. The feature you want is called "Eclipse XML Editors and Tools". Select it and hit finish.
Assuming it installs correctly, you will want to confirm that it didn't silently pull in JDT. Look at your Eclipse install in the plugins directory. See if you have org.eclipse.jdt.core plugin present. That's where the Java compiler lives.
Good luck and if you run into problems, a good place to ask follow-up questions is on the following forum. There a few people hanging out there that are pretty dedicated to the notion of some day creating an "XML IDE" eclipse distribution, so they should be glad to help you out.
http://www.eclipse.org/forums/index.php?t=thread&frm_id=88&
I would ideally suggest you to move away from eclipse, coz there are a ton of tools (Quanta Plus IDE, Bluefish etc) that provide you with great XML editing and validation feature.
However, this forum might help you -> http://www.eclipsezone.com/eclipse/forums/t40126.html.
You can un-tick Project > Build Automatically for automatic builds not to happen and even remove the buttons with the Run and Debug functionality in order not to press them accidentally.

Many Eclipse installations, or how to install many development tools on one Eclipse?

HI all,
I have Eclipse installed with PDT (PHP Development tools).
I want to program in Java and C++, do I have to download whole Eclipse JDT and Eclipse CDT again, and have separate installations, or can I install "plugins" to handle Java and C++ ?
Thanks
Yes you can install the plugins into the same Eclipse installation. For Helios you can use the Update manager Help->Install New Software then select the Helios site and select C/C++ in Programming Lagnuages and so on. If there's something else you need you need to get the update URL and add a new site.
You can have one eclipse with all the plugins (and perspective). But that's tedious:
you'll have to find the plugin jars for each of the 'suites' and place it in the plugins dir. Sometimes they might not have an update site url
some plugins cause problems, sometimes mixing certain plugins cause problems - in short, the more plugins, the more likely your environment will crash
The way I'd suggest is to have a separate eclipse installation for each task. I myself have 3, for different sort of java development (one java, one flex, one for specific project with specific plugins)
Eclipse itself is perfectly stable and capable of supporting quite a lot of plugins. However if you are unlucky to need "crappy" plugins, there the problems being.