Can't get eclipse to recognize my plugin - java

I exported my eclipse plugin through the "Export Wizard" in the manifest and seems like everything went well (no errors). It created a .jar file within a plugin directory in a zip file.
I thought putting the jar into my Eclipse plugin directory would install it (after re-launching eclipse) but that didn't work. Eclipse can't see the plugin (the perspective isn't showing up)
I tried with Help->Install new software->local archive but it keeps saying "no software found"
Can you help me getting my plugin ready to be installed on a fresh Eclipse copy?
Ps. my plugin uses other dependencies like EMF/GMF

In eclipse, go to your console window. From the drop down meny, select OSGI console. Run the command ss or ss <name of your plugin>
You will then see the state of your plugin and a number. The state will probably be "installed" which means if has been found, but some dependencies were not satisfied.
Run the command diag <number of your plugin> and you will see why it wasn't started.
For more details, see Wheres my bundle
Edit: A first step to verify that the plugin is working would be to start up a new eclipse instance with your plugin. In the run configuration dialog, there is a tab with all the plugins that should be started. Make sure yours is checked and it will start with the new eclipse instance.

If you are using Eclipse 3.4 or above, put your plugin in the 'dropins' directory.
To install via Help->Install new software you need to create an 'Update site' or a 'p2 repository'.

By far the most ellaborate descriptions of installing your plugin is provided by Vogella deployment of your plug-in
It covers all 3 possible ways in which you may install your plugin detailing the pros & cons of each of the following approaches :
1 . Installing your plug-in from your Eclipse IDE
2 . Export plug-in and put into dropins folder
3 . Create update site for your plug-in

Sometimes you just have to restart Eclipse. File -> Restart and try again. Worked for me because Eclipse was caching the results of my local update site.

Open plugin.xml
In "Overview" Tab in "Exporting section" go to "Export Wizard"
In "Export" window in "Destination" section choose "Install into host. Repository" and choose dir which will looks like "xxx/.metadata/.plugins/org.eclipse.pde.core/install/"
Press "Finish" button
Wait for Export to finish without any problems
Restart Eclipse

Related

How to install a Plug-in project to my Eclipse? (Version: Luna Service Release 2 (4.4.2))

I have generated a demo popup menu plugin project automatically by Eclipse. Here is the project structure,
I have set a objectContribution to the point org.eclipse.ui.popupMenus,
When I right click the project and choose Run as -> Eclipse Application, another Eclipse process run and I can see the configured menu works well,
How can I install this plugin for my original Eclipse process?
What I have tried
I did some research and tried to Export -> Deployable plug-ins and fragments, then put it into the %EclipseFolder%/plugins, but it didn't work. I also have tried to Export -> Deployable features and installed it by Help->Install New Software, also failed to see the menu when right click the project.
Will you please help? BTW, I would like to know how to contribute a menu which will display when I right click on a package in a project? Thanks so much.
Use the Deployable plug-ins and fragments wizard and select Intall into Host on the Destination page.
This will create a p2 repository at the denoted location and install the selected plug-ins from there into the host instance, i.e. the Eclipse IDE that you are currently working with. I think a restart may be required.

Uninstall plugin of eclipse without open eclipse

I have installed a new plugin for eclipse and since then when i opened eclipse after a few seconds it's not responding.
Is there a possible way to get rid of this plugin without open eclipse?
Thanks,
The p2 Director application can do it, but it's not trivial. It's documented (somewhat) at http://help.eclipse.org/luna/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html
Another option is to try opening on a brand new workspace; sometimes it's the workspace that causes a problem, not a plug-in by itself.
Final option is to just delete your Eclipse installation (not your workspace), and re-extract a clean copy. Since Eclipse "installation" is just a zip/tar extraction, it's not hard to do. You would just need to re-install any third-party plugins that you already had and wanted to keep.
Open Eclipse installation folder, find plugins folder, find the plugin and delete it manually. Then do the same in features folder.
Backup everything before, because you might delete something that belongs to Eclipse. This will sometimes require that you run eclipse -clean from your command line/terminal to truly get rid of the plugin.
As described here, you could use Eclipse from the command line with the Eclipse Directory and -uninstallIU option.
For example,
eclipse -nosplash -application org.eclipse.equinox.p2.director -uninstallIU org.junit

Eclipse Debug: Source Not Found while remote debugging

In my Java eclipse project, while I am remote debugging, eclipse does not step into the class files of imported library files even though the source file jars are properly mapped to the library files.
Instead it gives me a "Source Not Found" error. But when I am editing the same class in eclipse, I can control-click a class or method name and it takes me to the correct library class file.
Can anyone please tell me what I am doing wrong?
I am using Tomcat 6 and latest Eclipse Java EE.
In this scenario just follow the following steps:
Go to Run → Debug Configurations
Select the remote application configuration being debugged.
Select the second tab named 'Source'
Now add the folder/projects containing the source code explicitly here.
In the Java build path for the project, under the sources tab, check if your class path is under the included list. If its under the excluded list, remove it from there.
As Saury said, get your debug configuration right. When remote debugging, often developers have selected the wrong project while creating a new configuration. Verify you select the project you wish to debug and it corresponds to the version of the deployed WAR/EAR/JAR in the appliation container.
I faced same issue and got solved by below steps in eclipse.
Go to Severs tab in your Eclipse tab
Right click on the server and click on Add and Remove Projects
Select/add the project EAR which you want to debug
After finish - Start your server in debug mode
Should solve with above steps as it resolved for me:)
I ran into a similar problem. It turns out I was missing the devel package on CentOS.
In my particular case, the following yum statement solved the problem.
yum install java-1.7.0-openjdk-devel
Follow the next steps in case you use a parent project connected to sub-project/s:
Use the 'Debug Cofigurations' source tab or the 'Edit Source LookUp path' option to attach the sources of the running code.
Note: you'll need to attach the src folder of your inner project rather than the target in order to make it work (check the screenshot below).
E.g.
An update for eclipse Oxygen (Feb 2018):
Attaching the Java projects (sub projects) also worked well; e.g:
Check under "Debug Configurations" -> "Remote Java Application" -> Tab "Connect" -> "Project" that you chose the correct project.
Here is how it worked for me. Did this on Eclipse oxygen
Go to debug configurations and then the source tab
Click on Add
Select Java Library. Hit ok
The select Web app libraries and click next
In the next screen select the project/application that you are
debugging.
Click Finish
This worked for me like a charm
Using Eclipse version Oxygen.2 (2017), the accepted answer did not work for me. The following procedure was successful.
Launch the application to debug with the Xdebug and Xrunjdwp switches.
cd "C:\Program Files\Test_742\Test 7.4"
test_app.exe -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8500
Create a new workspace in Eclipse.
Create a new Java project using File -> New -> Java Project.
Copy the source code of the Jar to debug to the src folder of the new project. I found it necessary to ensure that I copied the complete folder hierarchy of the source code to my source folder.
For me that meant copying \com\test... to my src folder.
This puts all the source code in the build path.
Copy any dependency JARs to the project. I created a new folder named myJARs.
Refresh Package Explorer to see the new myJARs folder.
Add the dependency JARs to the build path by opening File -> Properties -> Java Build Path -> Libraries (tab), and click Add JARs...
Add each dependency JAR to the list, then click Apply and Close. This adds the JARs to Referenced Libraries.
Configure a debug session. Click Run -> Debug Configurations -> Remote Java Application. I set Connection Type = Standard.
Configure Host to point to the machine running the JAR and Port to the port specified in the address portion of the command line switches (8500 in my example).
Notice that on the Source tab, both the source files and the dependency JARs are present.
Click Apply, then Debug.
View the debugging perspective by clicking Window -> Perspective -> Open Perspective -> Debug.
Place breakpoints in the source code.

How to upgrade the ant built into eclipse?

I use ANT for all my builds and I also use eclipse as my IDE and I would like to be able to use the latest version of ANT in my eclipse, frequently the ANT that ships with eclipse is a point release behind. so my questions are.
Is there an easy way to get the eclipse ant plug-in to use the latest version of ANT?
Is there any easy way to add extra custom ant libraries to the built in eclipse ANT plug in, as I would like to be able to add things like the subversion task to my ant build and have it accessible from within eclipse.
Download and unpack the latest ant build anywhere on your hard disk, then run Eclipse, and go to
Window > Preferences > Ant > Runtime
and click on the button called
Ant Home
Browse to the ant folder that you just unpacked, and choose that folder. Now Eclipse will use this version of ant instead of the built-in ant. I use this way, and actually prefer it, because now I have the same ant version in command line and in Eclipse
In the same window you can add any other jars with 3rd party ant tasks, and they will be used by ant (just 'add jars'/'add external jars')
While not easy, by my standards at least, this is the way to update the ant plugin. At least for RAD 8.5, I'm sure eclipse is similar.
Go to Help -> About RAD -> Intallation details -> Plugins ... locate the org.apache.ant plugin version you are using. Note the Provider ... in this case for me it was Eclipse Orbit.
Next you need the repository URL for Orbit, googling got me this page.
http://wiki.eclipse.org/Orbit/FAQ
Which describes how to locate the repository.
Find the Orbit build drop that you need here:
http://download.eclipse.org/tools/orbit/downloads/
Add 'repository' to the URL of the drop. For example, for the drop in
http://download.eclipse.org/tools/orbit/downloads/drops/S20101204061544/
the URL that you would use is:
http://download.eclipse.org/tools/orbit/downloads/drops/S20101204061544/repository/
I personally went with
http://download.eclipse.org/tools/orbit/downloads/drops/R20130827064939/repository
Next, if you are behind a proxy, make sure that your proxy config is correct and the IDE can connect to the internet.
Then go to Help -> Install New Software
Next to the Work With dropdown hit the Add button and enter the repository information.
Select the apache bundle from the list and complete the steps of the wizard to perform the update.
Now that the repository is added to the list, for future updates you can use the Help -> Check for Updates menu item.
Good Luck, took me a day to figure that out and work through it.

Help installing PMD Eclipse plugin

I am trying to install PMD onto my Eclipse Helios installation. I follow the usual instructions to use the 'Install New Software' feature within Eclipse. All seems to go swimmingly and the installation completes. After restarting Eclipse, the option to use PMD is not there as expected (by right-clicking on a project).
Could someone advise on any steps I may have missed? Eclipse is the 20100617-1415 version installed on Red Hat running KDE.
Any guidance will be appreciated.
Thanks
Either the PMD plugin had an error on installation, or there was a problem when trying to start the plugin up. Either way, there should be something in your error log.
I'd first check there to see if something relevant in the log (open the Error log view). If not, then you can check to see if the plugin is actually installed. Click on Help -> About Eclipse -> Installation Details -> plugins and look for PMD.
If it is installed, then try uninstalling and reinstalling it. If the PMD plugin is not installed, then something failed.
Make sure that your eclipse/ directory is writable for the current user (while not a hard requirement, many plugins do need this for some reason).
Unfortunately it is not possible to install PMD from the Eclipse Marketplace.
Only way: Help > Install New Software... > Add... > http://pmd.sourceforge.net/eclipse
Maybe you have installed eclipse-pmd instead of PMD. It'll be avalible only in the project's properties option.
You can better try to install from http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/
But, make sure the Window-Preferences-General-Network Connection is "Direct" and "Native".
And restart. You'll surely find the PMD in preferences. I did for Keplar and works fine.
To install the PMD plugin for Eclipse:
Start Eclipse and open a project
Select "Help"->"Software Updates"->"Find and Install"
Click "Next", then click "New remote site"
Enter "PMD" into the Name field and
"http://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/"
into the URL field
Click through the rest of the dialog boxes to install the plugin
To configure PMD, select "Windows"->"Preferences", then select PMD.
To run PMD, right-click on a project node and select "PMD"->"Check code with PMD".
For more info refer LINK

Categories

Resources