I'm developing an Eclipse Plugin which is supposed to have a menu with two commands, by clicking on each command we should call the corresponding Plugin, both those Plugins are packaged as jar files.(so command1 calls plugin1.jar and command2 calls plagin2.jar)
How can I implement this? is it even possible?
Yes this is possible. The basic design of commands in Eclipse allows commands to be defined in any plug-in, and their handlers in any plug-in too (not necessarily the same one even!).
One menu, popup-menu or tool bar within Eclipse can be populated by any plug-in by contributing using the URI mechanism.
I recommend you start with some Eclipse Commands Tutorials, such as http://www.vogella.com/tutorials/EclipseCommands/article.html so that you can find more specific questions we can help with.
Related
I installed Java extensions like maven, spring-board, Java, etc.
And vscode shows-up these extensions all the time in side-bar like in attached screen-shot.
Is it possible to items like JAVA PROJECTS, MAVEN, SPRING-BOOT DASHBOARD when I work on non-Java projects (like when I open a Python project)
I know that I can hide them manually by clicking on ... at top-right.
Want to know if I can get this done automatically.
thanks,
The team is actually doing such works right now, I believe some of them will be available very soon. Here are some issue links:
https://github.com/microsoft/vscode-maven/issues/549
https://github.com/microsoft/vscode-java-dependency/issues/372
https://github.com/microsoft/vscode-java-test/issues/793
I am a newbie to Eclipse. I have some plug-ins installed in my eclipse workbench along with their source plugins (thus i have attached code with these plugins).
How can I open(and view) the source code of these installed plugins and set break-points so that I could debug these plug-ins?
My motive behind this task is to get a deeper understanding of the source code of some of these plug-ins.
Though the post How to set a breakpoint in Eclipse in a third party library? explains some methods, it doesn't tell how to open and view the attached source code.
Thanks in advance.
If you only need breakpoints, use Ctrl-Shift-T (Open Type), enter the name of the class and set the breakpoints.
But if you really want to learn about the plugin in question, there is more: Open PDE perspective, there is a view "Plugins". Select the plugin you are interested in, choose Import->As Source from the context menu of the plugin. This imports the plugin into your workspace, so you can really investigate all artifacts inside, not only the source. By default, your launch configuration will use the plugins from the workspace as first choice, so you can even modify that imported plugin now and see the effects when running your workspace.
I have the source code for the VersionOne plugin. I am wanting to modify the code because I am getting a NullPointerException when I click a specific button on the plugin which crashes eclipse. I was wondering what steps I need to take in eclipse to import the source code, modify it, and get it to run. I have read over how to create a new plugin project, but I have never tried importing a plugin before. Plugin Source
Once you have imported the project and that seems to work fine, just run it like any other plugin.
I.e:
Set the breakpoints you want in the code
Click the "Run as..."
In the run dialog start up a new Eclipse instance
On the tab "plugins" make sure your imported plugin is selected
If you are using the plugin at the same time, make sure that the non-workspace is not selected
In the new Eclipse instance, set up a situation that will provoke the bug
You need the following things to do that:
From Eclipse download a distro with PDE (Plugin Development) included.
The source pages
Some configuration management tool like Git or Subversion.
You do then the following steps:
Unzip your sources locally somewhere and add them to the CM system.
Create an eclipse plugin project from that source location (depending on Git or SVN different steps).
Create a run configuration for Eclipse that includes that plugin. That is similar to creating a run configuration for Java, but your Java application is then eclipse (see the Help on Eclipse Application Launcher). You have to ensure that in the "Plug-ins Tab", your new plugin is included. After you have started it, you should see the new feature implemented in the new running eclipse. To debug it, you just have to press the debug button instead of the run button. You may then add breakpoints to the source code of your plugin to see how it is working.
You are then able to start a new eclipse application which includes the plugin and make your tests there. You are able to set breakpoints, debug the code and so on. If you find the error, you can change the code, test it, and as a result have a difference to the source you had initially. The best would be then to make a patch and send it back to the originator.
To deploy it then to others is a different story, and is well documented.
On my Mac computer, I follow the tutorial on this page to get the Taipan example run, but still failed so many times.
Switch to the Plug-in Development perspective and open the models folder within the org.eclipse.gmf.examples.taipan project. Explore each of the models found hereand their element properties. You'll notice that there are full and RCP versions of the generated Taipan examples to explore.
When I try to run as "Eclipse application", it launches a new eclipse app but the dialog box Examples does not have the 'Taipan Diagram' as it says:
create an empty project and a new 'TaiPan Diagram' found in the Examples folder of the New dialog
What are the possible causes? Someone helps me to solve it out?
I'm assuming that your plugin is working fine and doesnt show compilation errors?
Then the most likely reason is that you havent chosen your plugin to be active in your launch dialog.
I answered a similar question with this:
My guess is that you have just created the plugin, but aren't running it in your current Eclipse instance. That can be verified by opening the view "Plugin registry". That will show a list of all plugins, see if the plugin you have created is in that list.
If you click on the run button in Eclipse you will open a run configuration dialog. In one of the tabs, you get to choose what plugins should be available. Make sure your plug-in is selected. This will start up a new Eclipse instance that will run your plugin.
To make your plugin be a part of your ordinary Eclipse installation, you will need to export it to a jar and copy that jar to the dropins catalog.
Is there any role for the Project menu when working with StatET and Eclipse using Sweave and R?
If so, are there any learning resources that explain how this might work?
Do these menus offer anything over and above a makefile?
I'm curious to learn more about building moderately complex Sweave/LaTeX/R projects.
Specifically, the Project menu has options Clean... and Build Automatically which intrigue me.
I'm curious to learn more about building moderately complex Sweave/LaTeX/R projects. Specifically, the Project menu has options Clean... and Build Automatically which intrigue me.
Hi Jeromy, I never managed to properly setup R and Eclipse, so I will only give you a partial answer.
Generally the Clean command is used to remove the compiled files from a project, so I assume it will delete any .ps or .pdf file generated by Eclipse.
The Build automatically setting (which is an on/off switch) rebuilds the project every time you save a file.
As a side note, to generate reports I use the combo LyX + Sweave that works very well. And for R scripts I find Gedit + RGedit nice and lightweight.
I don't know the internals of Eclipse very well, but I think these menu items are there for generic Eclipse projects that can link to the utilities that build your 'project' from 'source'. Looking under Project > Properties > Builder shows one builder configured, 'R Internal' that is not configurable or editable.
Personally I've never used a makefile for Sweave document creation, instead using the External Tools menu to setup the process for building a sweave Rnw file into a PDF. (under Run > External Tools > Configure External Tools. Also see here). This has worked well for me.
Have you considered asking your question on the StatEt mailing list ?