I had a supercool hook set up on Eclipse to compile my project's .css theme file from its .less modules every time a .less module was modified by monitoring those resources through an "external tool configuration".
I could select which resources to monitor for triggering the nodejs less compiler tool on the launch configurations build options tab.
On eclipse Mars there is no such tab.
It really bothers me to loose this automation. Does anybody know where did that tab go or how can I keep this functionality without it?
You set up such custom builders via the project's Properties dialog. Open the properties, then select the Builders section. There you can use the New... button to configure a Program to run as a builder.
Related
How can I configure MyEclipse and the SVN plugin (Subclipse 4.3.3) so that my Run Configurations are included in the source code control. Every time a new developer checks out the project, he doesn't have the Run Configurations needed to test the application properly or to do the Maven packaging correctly.
Is there a way?
To share your run/launch configuration, go to the launch configuration (Run > Run Configurations...) tab Common for Save as choose Shared file (instead of Local file).
In addition, you can choose to Display in favorites menu to add it to the drop-down of the corresponding button in the main toolbar.
Is there any option in IntelliJ IDEA to create a configuration to run an external jar like the external tools configurations in Eclipse?
IDEA does not have a dedicated "Executable JAR" run/debug configuration. It does sound like a nice new feature. I'd recommend you request it: http://youtrack.jetbrains.com
Despite that, there are two options to run an executable JAR.
OPTION 1
You can define a normal application run/debug configuration and define the executable JAR via the VM options. Here's an example:
OPTION 2
You can create an "External Tool" definition via File > Settings > [IDE Settings] > External Tools. (Click the Help button in the dialog for details on the fields). You can run it via the Tools menu, or by assigning it a keyboard shortcut in the Keymap settings. The one downside here is that External Tools are defined at the IDE level and not a Project level. So that definition will show for all Projects. However, using the "Groups" option in the External Tools to group all configurations for a Project can add some structure.
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.
My eclipse is constantly running "Build Workspace" tasks. It is not a long running builds, more like 1 build a second.
Sometimes I'd see 10 "Build workspace" tasks sleeping and waiting in the Progress tab.
I'd like to know what is triggering those builds. I have many plugins installed.
What is the way to troubleshoot this?
Here are some steps to help you debug what is going on.
Download the Eclipse Classic SDK for whatever version of Eclipse you are currently using. For Juno that link is here.
Open the eclipse.ini for your current normal eclipse and add the following options: -Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000
Start your Eclipse instance that you want to debug, it should pause at the splash screen
Unzip the Eclipse classic SDK and start that Eclipse instance
Open the Plugins view
Find org.eclipse.core.resources
Right click and select "Add to Java Search"
Open Type dialog, type in "BuildManager"
You should see a class from that plugin be given as an option, then open it
Find the line that looks like: prereqs = currentBuilder.build(trigger, args, monitor); It should be about line 728 (For Eclipse Juno)
Set a breakpoint here
Create a new Remote Java Application debug configuration and point to localhost port 8000
Launch this debug configuration
You should see your other Eclipse instance startup
Now every time the Eclipse build manager fires off a build (which should happen on all of those Build Workspace jobs), then you will see this breakpoint be hit and you can find out what builder is firing.
Update 1
If you need source to other Eclipse bundles they can also be added in the "Plug-ins" view. Select all the plugins there and right-click and use Add to Java Search
What plugins do you have installed that are currently active?
Press CTRL+3 type "plugin" and then choose plugin registry.
In the plugin view right click and choose "Active Only"
Check the non-essential core plugins (for example related to servers which automatically build & publish)
Post a screenshot of active plugins if you need any more help
You may have build automatically checked which will build when you save. Check under the nav Project > Build Automatically
Other way to close all unused projects.
Further, for good view, use filtering: View Menu -> filters -> Check 'Closed Project'.
Sometimes if you have > 20 opened projects you can observe constant 'build workspace' tendency.
I'm a bit new to building Eclipse RCP applications, and I'm finding it necessary to validate the list of plugins in the Dependencies tab of the .product file. But Eclipse (Indigo) offers no tools to help. In the launch configurations, there are great tools in the Plug-ins tab (buttons Add Required Plug-ins and Validate Plug-ins). It seems like there are 2 really obvious solutions that just aren't available:
Add a new button (or something) to copy the exact list of plugins from a .launch into a .product file (I tried to manually copy the text of the backing files, but the xml formats differ), or
Put the same two buttons in the Dependencies tab of the .product file.
I'm only creating one simple plugin, and the dependency list has 300 entries... very tedious to manually compare with a .launch! Am I missing something, is there actually a way to validate these dependencies directly in the .product file? Thanks for your help.
Byron
Here are two posibilities to get what you want:
Create a new product configuration
In the New Product Configuration dialog under Initialize the file content select Use a launch configuration and choose your Plug-In's launch configuration
Open the *.product file, switch to the Dependencies tab and you can see all Plug-Ins which are required to run your defining Plug-In
Edit an existing product configuration
Open the *.product file, switch to the Overview tab and select your Plug-In's launch configuration under Product Definition / Application
Switch to the Dependencies tab and add your defining Plug-In via the Add button
Select the Include optional dependencies when computing required plug-ins checkbox (which you can find at the bottom)
Hit the Add Required Plug-Ins button and you can see all Plug-Ins which are required to run your defining Plug-In