According to this link
It seems easy to setup the environment. Into the last paragraph:
Setup the Run Configuration
There should be a misterious EclipseTrader run configuration appearing from nowhere !!
Obviously there is no such thing !!
The question is, how can I debug an eclipse within another elipse ?? Is it possibile ?
If you don't have the Eclipse application entry in the available debug configurations then you should probably be running an Eclipse which does not have the plug-in development environment (PDE) installed.
You can either download the Eclipse classic package which already contains PDE from the download page or install the PDE plug-ins in your current Eclipse platfom from the Eclipse update sites.
Related
I am currently working on eclipse plug-in that involves many modules, and I would like to debug and run this eclipse plug-in from IntelliJ.I open this project in IntelliJ to edit code but when I have to run/debug this project I have to open eclipse IDE and start it from there. How can I use IntelliJ to do this?
I haven't actually tried this ... but you could try launching the RCP application stand alone but with the remote debug parameters specified for in your application's .ini file.
Then just point IntelliJ to the appropriate source and attach it's debugger to the running app.
Why do you want to do that? Eclipse has multiple tools for the plugin development that you will miss in IntelliJ. Also you need to build your plugin as product headless and then attach a debugger to it.
In my opinion it doesn't worth the effort. I would install Eclipse and devolop with eclipse.
This is my first attempt at creating an Eclipse plug-in. I've created one, along with a feature and update site. I set the target platform as my local Eclipse installation. When I run/debug the plugin from within the development environment everything works fine.
Now, my colleague installed the plug-in from the update site that I hosted. When he starts using any of the functionality exposed by my plugin he gets runtime exceptions.
He sees null pointer exceptions which didn't occur when I ran my plug-in project from my development environment.
I have a wizard that's part of my plug-in. When he close it he gets a "Unhandled event loop exception", and the wizard doesn't close. I didn't have this issue when I was running/debugging my plugin in my development environment.
Now I'm confused as to why the same plug-in is behaving differently in the production environment, as against the dev environment and when I was debugging it from my IDE. The target platform in both cases is the same Eclipse version. What could be the reasons?
And how do I debug the plug-in in a production environment? Is there a remote debugging capability for debugging the plug-ins on the production environment?
Any suggestions would be really useful!
To remote debug your plug-in, first add debug arguments to your target Eclipse .ini file
-vmargs
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
before launching it.
Then open another Eclipse instance with a workspace containing your plug-in project.
Open Run > Debug Configurations..., select Remote Java Application and create a new configuration.
As Project, browse and select your plug-in project.
Also fill in your connection properties (host of target Eclipse and port 1044).
Launching the newly created debug configuration allows you to debug your plug-in the same way you debug locally.
Now I'm confused as to why the same plug-in is behaving differently in
the production environment, as against the dev environment and when I
was debugging it from my IDE. The target platform in both cases is the
same eclipse version. What could be the reasons?
This is a classic: Eclipse plugins and RCP applications do indeed behave differently between PDT (the Eclipse IDE) and the exported product.
In your case, a NullPointerException thrown from the exported version but not from Eclipse is 9 times out of 10 an image or other resource files (properties, etc.) that is loaded by your code but is not listed in the build.properties of your plugin.
Anyway, you'll need to check the logs to retrieve the stacktrace and hunt down its cause. Such logs could be found in your friend's workspace under le .metadata/.log file
From your development workspace as it stands now, use the "Debug As -> Eclipse Application" menu item to startup a test workspace. When it starts up, you'll have two workspaces running: the original development workspace and the new test workspace. You can set breakpoints in your plugin code in the development workspace and run your plugin in the test workspace.
When your plugin execution in the test workspace gets to one of your breakpoints, execution will pause and you can use the Debug view in your development workspace to look at variables, set more breakpoints or anything else you want to do to debuf your plugin.
See the Apache Wiki for Developing with Eclipse.
Under Windows 10 with Tomcat running as a windows service I started:
tomcat8.5\bin\Tomcat8w.exe
& added in the Java tab as the first entry in Java Options to enable remote debugging:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
I want to create a java webstart product that includes all of the contents of my current eclipse installation - standard eclipse java edition with some extra plugins that I have developed/downloaded.
There are a number of tutorials showing how to do this for an eclipse RCP application, but I don't want to create an RCP specifically for this purpose (I also tried to do it and never really managed to configure the app to look just like my workbench).
So, is this even possible? Any pointers?
Update: I followed this article, but after deploying my application in the web server and running the jnlp, the jars were downloaded but nothing happened. I tried changing the eclipse.product property to other "possible" values, but didn't help.
Do you really need the web start software?
Since eclipse doesn't requires installation, and the plugins are installed in the same directory of eclipse why don't you zip your eclipse once you have it configured, and redistribute it as a zip. Even eclipse itself is distributed as zip.
I'm sorry for a pretty vague title, didn't want to turn it into a paragraph.
So, I am using Eclipse Platform 3.7.1 (the one with absolutely no plugin preinstalled), the latest version so far, and I have discovered that by taking advantage of its -configuration option, I can choose which plugins are running and which are not. It was going well enough until I started installing the plugins.
But allow me to explain my setup first, I am using Ubuntu linux by the way. Using only one eclipse installation, my installation is arranged in the following order:
Installation:
~/bin/opt/eclipse
eclipse (executable binary)
~/bin/eclipse -> opt/eclipse/eclipse
Configurations:
~/.eclipse/configuration
web-php
android
java
Installing JDT and ADT while running eclipse and using the android configuration directory posed no problems. So I moved on to the php configuration and tried to install PDT (the JDT and ADT plugins were not activated here, so far so good). The problems came along after the installation, not only was I not able to use PDT, I noticed in the Installation Details that JDT, ADT, PDT were installed but not activated. Instead, they were all activated in the android configuration. To make it worse, when I chose the Java configuration, I could not even use JDT.
My expectations however were when using:
eclipse -configuration ~/.eclipse/configuration/android
was that only the JDT and ADT were activated and when using:
eclipse -configuration ~/.eclipse/configuration/web-php
only the PDT is activated
Regarding the java configuration however, it's probably another problem altogether but if there was help on how to activate a plugin installed from another configuration, I'd deeply appreciate it.
Also, see Single Eclipse install with multiple Configurations and Workspaces
In a p2 world there are extra steps to isolate bundles from each other. You need not just a different configuration directory, but a different p2 profile.
Have a look at the config.ihi in each of your configurations. There are two ways that Eclipse identifies the plugins to use, the ..updateconfigurator, which simply uses all of the plugins in the plugins folder, and the ..simpleconfigurator which uses the bundles.info file in that's in the org.eclipse.equinox.simpleconfigurator folder (which is maintained by the p2 installer). Make sure this file is what you expect.
And also, you might want to start with the -clean option if you are using the updateconfigurator to have it rescan all of the plugins (otherwise it remembers in some hidden cache).
Make sure when you installed everything that you had your -configuration set to the right place for the different things you installed.
I hope some of this points you in the right direction.
I'm trying to install the WTP (web platform tools) to my Eclipse installation so I can get the XSL transformations working. The base Eclipse they installed for me here was the plain Java IDE (the splash screen says "Ganymede" if that means anything). Looking at this site, the URL to get the download should be here: http://download.eclipse.org/webtools/updates/ ...But when I give that URL to the Eclipse update manager, I get an error telling me: "No repository found at http://download.eclipse.org/webtools/updates/"
Anyone else had this problem? Anyone know what might be up? Anyone know how to get the xsl-transform plugin installed?
EDIT:
I should have mentioned before that I want to find a way to do this without installing any new instances of Eclipse. This process will eventually be sent to several other developers who already have Eclipse (same version that I'm testing with) and I'd rather just do an in-place upgrade rather than have everyone go and install a new product.
UPDATE:
I found another plugin, Xcarecrows 4 XML which can also do XSL transforms. The interface is ugly and seems more than a little quirky, but it's also a small download, and at least it runs and transforms. Unless I can find an easy way to get WTP working, I'll probably just stick with this.
You can try and install WTP through the main Ganymede update site:
http://download.eclipse.org/releases/ganymede/
Or you can download the latest Java EE bundle and use that instead of your current Eclipse
(do NOT unpack it on top of your current Eclipse, but unpack it elsewhere, to test that second installation: it will come with WTP inside)
Note: check then "How do I start Eclipse" to point to your existing workspace in order to see all your previous project in your new Eclipse installation.
As mentioned in your link, XSL Tools is now part of WTP (for Eclipse 3.5 Galileo), and that may explain why your Eclipse Ganymede (3.4) might not interpret correctly the P2 update site for WTP (P2 being the new Eclipse provisioning mechanism introduced late in the 3.4 release cycle)
For Eclipse 3.5, you have an XSL Tools installation illustrated here:
But Eclipse3.4 is more likely to be compatible with XSLT0.5 and you will need a separate installation, because "XSL Tools" wasn't yet part of WTP.
I am not sure, however, where to find such an installation package within the Eclipse projects.
Use the following update site :
For Juno :
http://download.eclipse.org/webtools/repository/juno/
For Indigo :
http://download.eclipse.org/webtools/repository/indigo/
I'm assuming you don't have any firewall exceptions for Eclipse right?
The site for the WTP update is indeed the one you've listed. Maybe post a screenshot? You've added it specifically to your remote update site list?
Either way try a manual update which should be more reliable and get you up and running for now.
All-In-One Update (Eclipse IDE included):
Go to the Eclipse Download site.
Grab the all-in-one package: Eclipse IDE for Java EE Developers
Install, have a coffee and enjoy. (WTP is included)
Manual Update your existing installation of Eclipse:
Download the applicable WTP source package to your desktop
Shutdown Eclipse
Extract the package to your Eclipse installation directory
Startup Eclipse. (WTP is now available)
Follow the steps in the FAQ at http://wiki.eclipse.org/WTP_FAQ#How_do_I_install_WTP.3F .
Are you behind a proxy? If so, you need to make sure you configure your proxy settings in Eclipse.
Window > Preferences
General > Network Connections
Ok, I can probably get it working if I do a clean install of Eclipse. I can do that on my machine, but not the other team members' machines (at least not without going through many emails and paper work) so I'm going to say that XCarecrows 4 XML is the solution. It is able to do XSL transformations in Eclipse 3.4 and doesn't require anything else to be installed. Since XSLT is all I need, the plugin will do.
you can use the marketplace:
https://marketplace.eclipse.org/content/eclipse-java-ee-developer-tools-0
like the site says:
Drag to Install!Drag to your running Eclipse Workspace.