The other day I came accross this SO question : Bash script plugin for Eclipse? , the idea is great.
So I went to the download site downloaded this plugin but I didn't install any eclipse plugin manually so I don't really have a clue how to install one.
I extracted this zip file I downloaded and it looks like this :
What should I do next, how do I install this plugin ? thank you
When I try to install it using install new software from local dir I get this error :
Cannot complete the install because one or more required items could not be found.
Software being installed: ShellEd 2.0.0.201007201532-1--773533H735D97 (net.sourceforge.shelled.feature.group 2.0.0.201007201532-1--773533H735D97)
Missing requirement: ShellEd UI 0.0.0.201007201532 (net.sourceforge.shelled.ui 0.0.0.201007201532) requires 'bundle org.eclipse.dltk.launching [2.0.0,3.0.0)' but it could not be found
Cannot satisfy dependency:
From: ShellEd 2.0.0.201007201532-1--773533H735D97 (net.sourceforge.shelled.feature.group 2.0.0.201007201532-1--773533H735D97)
To: net.sourceforge.shelled.ui [0.0.0.201007201532]
PROBLEM 2 :
Cannot complete the install because one or more required items could not be found.
Software being installed: ShellEd 2.0.0.201007201532-1--773533H735D97 (net.sourceforge.shelled.feature.group 2.0.0.201007201532-1--773533H735D97)
Missing requirement: ShellEd UI 0.0.0.201007201532 (net.sourceforge.shelled.ui 0.0.0.201007201532) requires *'bundle org.eclipse.linuxtools.man 0.0.0'* but it could not be found
Cannot satisfy dependency:
From: ShellEd 2.0.0.201007201532-1--773533H735D97 (net.sourceforge.shelled.feature.group 2.0.0.201007201532-1--773533H735D97)
To: net.sourceforge.shelled.ui [0.0.0.201007201532]
I don't know what it means
I just successfully installed this using Drop-ins. It depends on DLTK & the linux tools man page plugin.
To install int Eclipse 3.6 Helios, Help > Install New Software:
Install DLTK Core from the Helios Repository: http://download.eclipse.org/releases/helios/
Install the LinuxTools Man Page plugin from: http://download.eclipse.org/technology/linuxtools/update
Download the ShellEd Update Site Zip, point the Update UI at the Archive and Install
Copy the complete folder (ShellEd-Update-2.0.0_M3) to eclipse/dropins. You should remove the site.xml file from the destination location and - I think it's still necessary - look into the features folder and extract all *.jar files (folder name = jar file name).
But you should be able to install the plugin from a local zip file source too. The "install new software" dialog should have an option...
For clarification - of course, manual installation is not recommended. You may have trouble with missing dependencies, although OSGi is pretty robust and eclipse won't crash. Worst case: the plugin will not install (from an OSGi perspective). So if possible, use "install new software" and install plugins from the vendors internet page. If not possible: manual install, unzip the jars in feature folder and, if it still doesn't work: start eclipse with the -console option and check the status of the installed plugins. OSGi will tell you, if a plugin didn't start and why.
The error message: The bash plugin depends on another plugin named ShellEd (Version: 2.0.0.201007201532). Looks like it is not included in the bash distribution and so you'll have to install it first (or together with bash).
You can find it here: ShellEd
This one is also required: Dynamic language toolkit (any version between 2.0 and 3.0). This was the hint: bundle org.eclipse.dltk.launching
Open Eclipse. Help->Install new software.
Add a new site, which should be local and point to your directory shown above.
Install the features it offers.
(Some of these options differ slightly in versions of Eclpse, I'm using 3.6.1 and that's how they are named there.)
I found http://sourceforge.net/apps/trac/shelled/wiki/Documentation/InstallGuide to be useful.
This is what worked for me in Indigo
Install DLTK Core from market place
Install the LinuxTools Man Page plugin from: http://download.eclipse.org/technology/linuxtools/update
Install ShellEd from https://downloads.sourceforge.net/project/shelled/shelled/ShellEd%202.0.1/update
Related
I am getting below error while installing Findbugs into Netbeans 8.2:
"There were some problems while storing Establishing a connection …
Cause: Cannot resolve external reference to m2:/org:ow2:asm:asm-debug-all:5.0.2:jar"
I have tried uninstalling NetBeans 8.2 and removing anything associated with the installation to get a fresh install with no success there, and I have tried the latest version of NetBeans 11.3 which I found does not have Findbugs available. I need the plugin for a school project and no one there has been able to help me with this issue either. Any help would be greatly appreciated.
I am using a Windows 10 PC.
Thank you.
The reason of the error
The error happens because when you download the plugin, NetBeans also tries to download additional dependencies. The links where to download the jars from are written inside the nbm package.
For example, one of the dependencies is asm-debug-all-5.0.2.jar, and the link is:
http://repo1.maven.org/maven2/org/ow2/asm/asm-debug-all/5.0.2/asm-debug-all-5.0.2.jar.
The maven repository is no longer accessible using the HTTP link. You can read more about it here.
So basically, you could not install the plugin because the plugin is outdated and contains invalid links for downloading dependencies from maven repo.
Before solving the issue, consider using SpotBug instead because the FindBug is outdated and is no longer actively maintained, for more information, please, see here in another answer. Also, keep in mind that it works only with JDK8.
How to solve it?
To solve the issue, you need to fiddle around a bit with plugins.
You need two plugins FindBug Libs (org-netbeans-libs-findbugs.nbm) and FindBug Integration (org-netbeans-modules-findbugs.nbm). Download them using thees links:
https://updates.netbeans.org/netbeans/updates/8.2/uc/final/certified/82/extra/org-netbeans-modules-findbugs.nbm
https://updates.netbeans.org/netbeans/updates/8.2/uc/final/certified/82/extra/org-netbeans-libs-findbugs.nbm
Unzip org-netbeans-libs-findbugs.nbm manually as if it is a simple zip file.
Edit the files in org-netbeans-libs-findbugs\netbeans\modules\ext extracted folder. In every file, you need to change the link from http to https.
Edit manifest file org-netbeans-libs-findbugs\META-INF\MANIFEST.MF. You need to remove all lines that contain CRS checksum. After editing it should contains only these lines:
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.9.2
Created-By: 1.8.0_45-b14 (Oracle Corporation)
Remover other two files in org-netbeans-libs-findbugs\META-INF (ORACLE_C.RSA and ORACLE_C.SF).
Zip it again.
After that, the file is ready for manually installing into Net Beans. Alternatively, you can download the file from here. I have already modified the plugin using the steps.
How to install and use it?
Got to Windows -> Plugins -> Downloaded -> Add Plugins
Manually add the modified org-netbeans-libs-findbugs.nbm file and click install.
Then add org-netbeans-modules-findbugs.nbm and click install.
When installing, it shows that it downloads the plugin, but actually, it downloads only dependencies. It can take some time.
After that, select your project in the project tree, make sure it was compiled before. Got to Source -> Inspect, choose FindBus in the Configuration.
After you click to inspect your report will be ready.
It works both on NetBeans 11.3 and 8.2. Make sure you are using JDK8 with NetBeans. I'm not sure it will work with the newest versions of JDK.
Here is an example with running it on 11.3 using JDK8 on some NetBeans module:
THE PROBLEM
I've been developing in Java for years, but a recent install of my tools on a new computer (Windows 10) has resulted in the strangest problem. When I create a new project, almost everything is underlined in red. The error reads Implicit super constructor Object() is undefined for default constructor. Must define an explicit constructor:
WHAT I TRIED:
A quick search online reveals that I should JRE System Library is most likely unbound, so I change it: Properties >> Java Build Path >> JRE System Library >> Edit:
All of the red lines go away, but I can't run my program. An Error reads:
An internal error occurred during: "Launching Main".
Model not available for helloWorld
On closer inspection, Eclipse shows an error in the src/test folder, but there are no files there.
When I restart Eclipse, all of the red lines reappear and I have to do everything all over again. It also cannot find the JUnit dependencies either, and I have to manually add JUnit 4 library to the build path.
DEETS YO:
OS Details:
Windows 10
Eclipse Details:
Version: 2019-09 R (4.13.0)
Java Details:
Java 13.0.1
Alright, so none of the posted suggestions worked but I independently found out what was wrong. In general, I've found that this solves a lot of weird Gradle activity, including the ominous "Could not install Gradle distribution from 'https://services.gradle.org/distributions/gradle-5.6-all.zip'" that a lot of people have problems with once they try to use Gradle with new versions of Eclipse.
Solution
When you install Eclipse, there's a Buildship Gradle Integration plug-in that is visible in the Eclipse Marketplace (it has a little graphic of an elephant next to it). When you get modern versions of JavaEE Eclipse, it comes with that installed.
The problem is that this isn't the most updated version of it.
So you have to click the button that reads "installed" and it'll update it. After you update it and restart Eclipse, your most recent version of Gradle will work.
When using gradle run this:
gradlew cleanEclipse eclipse
this will re-generate the eclipse project and this helped me
Under a fresh Eclipse, we encountered this "Model not available problem" on projects that do not use Gradle, but maven.
To update gradle did not change anything. We assume that there is a conflict between m2e and this plugin. We found 2 solutions :
A) Add gradle nature (even if unused)
Right-click on the project
Configure
Add Nature (elephant logo)
Run your app, enjoy
B) Uninstall gradle. (if not used and not mandatory for your eclipse version)
Help/Eclipse MarketPlace
Search "Gradle"
Go to "BuildShop Gradle Integration 3.0" (the elephant) which is indicated as installed and clic on the grayed installed button.
Uninstall it. It will restart eclipse.
Run your app, enjoy :)
In my case it is resolved by updating Buildship Gradle Integration 3.0 from Eclipse market place
i am updating android sdk 23 and i'm getting this error. I am using windows xp.
Error:
Cannot complete the install because of a conflicting dependency.
Software being installed: Android Development Tools 23.0.0.1245622 (com.android.ide.eclipse.adt.feature.feature.group 23.0.0.1245622)
Software currently installed: Android Developer Tools 22.3.0.v201310242005-887826 (com.android.ide.eclipse.adt.package.product 22.3.0.v201310242005-887826)
Only one of the following can be installed at once:
ADT Package 22.6.3.v201404151837-1123206 (com.android.ide.eclipse.adt.package 22.6.3.v201404151837-1123206)
ADT Package 23.0.0.1245622 (com.android.ide.eclipse.adt.package 23.0.0.1245622)
Cannot satisfy dependency:
From: Android Development Tools 23.0.0.1245622 (com.android.ide.eclipse.adt.feature.feature.group 23.0.0.1245622)
To: com.android.ide.eclipse.adt.package [23.0.0.1245622]
Cannot satisfy dependency:
From: Android Development Tools 22.6.3.v201404151837-1123206 (com.android.ide.eclipse.adt.feature.group 22.6.3.v201404151837-1123206)
To: com.android.ide.eclipse.adt.package [22.6.3.v201404151837-1123206]
Cannot satisfy dependency:
From: ADT Package 22.3.0.v201310242005-887826 (com.android.ide.eclipse.adt.package.feature.group 22.3.0.v201310242005-887826)
To: com.android.ide.eclipse.adt.feature.group 22.2.0
Cannot satisfy dependency:
From: Android Developer Tools 22.3.0.v201310242005-887826 (com.android.ide.eclipse.adt.package.product 22.3.0.v201310242005-887826)
To: com.android.ide.eclipse.adt.package.feature.group [22.3.0.v201310242005-887826]
I had the same problem, and was thinking of downloading a clean copy of Eclipse and then going through the installation of all the plug-in, but the sheer amount of hard work defeated my resolve.
I found another way out to update ADT 23 without any hassles on the current instance of Eclipse. :)
I was not sure if the approach will work or not, hence I did not capture the process, Please bear with me. In any case I can't post images I do not have reputation :P
Here's what I did:
Go to the Install new Software option from Help.
Open the available software sites.
Select Your Android site and remove it. Before removing copy the Location, we are going to use the same URL again.
Click OK (this will take you back to the previous screen).
paste the copied URL back into the "Work With" combo on the screen. Click Add.
It will flash a message saying it already has the options available.
Choose to uninstall the previous version and install new.
Voila, it installs ADT 23.
Hope that helps.
This seems to be a problem in the SDK tools rev. 23 update of Google. A lot of people have problems with this upgrade, see:
http://code.google.com/p/android/issues/detail?id=72584
http://code.google.com/p/android/issues/detail?id=72419
The only solution so far is to download a clean version of Eclipse.
I don't like to start with a clean copy and install all the other plugins, so I'll try to copy the SDK folders from this Clean Eclipse instance to your current one.
Edit:
I ended up with setting up a clean copy because I did not want to start more problems. I did the following:
download the Eclipse (luna) bundle you like to use: Eclipse IDE for Java Developers
install Android SDK
I could not update the SDK itself to version 23 so I had to do the following
download the Eclipse Android bundle
make a backup your current android-sdk folder
unzip and copy the sdk folder and copy it over the old android-sdk folder
(The new SDK folder only contains 4.4)
Now you should have a working eclipse and you can start installing all the other plugins you like to use again.
Have anyone gotten the release version of eclipse 4.4 to work with adt(Android development) and/or google web toolkit(gwt).
It seems like the gwt/adt plugins don't works with eclipse 4.4, so is there a secret place to download new versions or should I keep using 4.3 -(
Edit:
The reason I thought adt was not working was that the documentation(http://developer.android.com/sdk/installing/installing-adt.html) says that the plugin is called "ADT Plugin" which it is not.
Google just released its official SDK for Eclipse Luna: https://developers.google.com/eclipse/docs/getting_started
For adt ,
help -> Install new Software ->
https://dl-ssl.google.com/android/eclipse/ -> don't select everything
(it worked that way for me) i selected everything except Native development tools(i guess you don't need them if you debelop in java) and it's working well for me .
well… the gwt plugin actually can not work with luna release since it has a bundle dependency for eclipse core.runtime [3.8.0,3.10.0), here, ")" means it NOT includes 3.10.0 wihich is used in luna, however, it can been get rid of by modifying the osgi bundle file and then it will works fine with luna ,at least for me for now.
1 download the last update site zip file from google eclipse plugin site
2 unpack it
3 then you will need to modify 2 files firstly
an osgi META INF/manifest file included in a jar named *gdt*e42 (sorry, forget the full name, you can find it when you are trying to install the plugin, luna will complain that some dep bundle is missed)that is located in plugins dir, just change core.runtime version from 3.10.0) to 3.10.0]
another one should be contents.jar (maybe artifacts. jar), same above
now you can install the plugin if you have already have the eclipse RCP installed
however, install will failed because the md5 hashing is changed,
finally, copy the expected md5 from error message dialog to replace the old md5 value in artifacts.jar(maybe contents.jar)
now reinstall the plugin ,it should work for now
UPDATED:
maybe you should remove the bundle-version from MANIFEST.MF at com.google.gdt.eclipse.platform.e42 jar
and change the version to "0.0.0" from content.xml at content.jar
If you are using the Help----->Install New Software option, you might encounter this error message just like i did trying to install the Android plugin.
An error occurred during the org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase.
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust, operand=, action=).
Error reading signed content.
error in opening zip file
My solution was to go through Help-->Eclipse Marketplace and then search for "Android" Select the plugin from the search result and install it from there.
Cannot complete the install because of a conflicting dependency.
Software being installed: Android Traceview 16.0.1.v201112150204-238534 (com.android.ide.eclipse.traceview.feature.group 16.0.1.v201112150204-238534)
Software currently installed: Eclipse IDE for Java Developers 1.3.1.20100916-1202 (epp.package.java 1.3.1.20100916-1202)
Only one of the following can be installed at once:
Eclipse UI 3.6.1.M20100826-1330 (org.eclipse.ui 3.6.1.M20100826-1330)
Eclipse UI 3.6.2.M20110203-1100 (org.eclipse.ui 3.6.2.M20110203-1100)
Eclipse UI 3.6.0.I20100603-1100 (org.eclipse.ui 3.6.0.I20100603-1100)
Cannot satisfy dependency:
From: Android Traceview 16.0.1.v201112150204-238534 (com.android.ide.eclipse.traceview.feature.group 16.0.1.v201112150204-238534)
To: org.eclipse.ui 3.6.2
Cannot satisfy dependency:
From: Eclipse IDE for Java Developers 1.3.1.20100916-1202 (epp.package.java 1.3.1.20100916-1202)
To: org.eclipse.epp.package.java.feature.feature.group [1.3.1.20100916-1202]
Cannot satisfy dependency:
From: EPP Java Package 1.3.1.20100916-1202 (org.eclipse.epp.package.java.feature.feature.group 1.3.1.20100916-1202)
To: org.eclipse.platform.feature.group [3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L]
Cannot satisfy dependency:
From: Eclipse Platform 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L (org.eclipse.platform.feature.group 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L)
To: org.eclipse.rcp.feature.group [3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T]
Cannot satisfy dependency:
From: Eclipse RCP 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T (org.eclipse.rcp.feature.group 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T)
To: org.eclipse.ui [3.6.1.M20100826-1330]
May be you are doing something wrong. below are the basic steps.
Start Eclipse, then select Help > Install New Software....
Click Add, in the top-right corner.
In the Add Repository dialog that appears, enter "ADT Plugin" for the Name and the following URL for the Location:
https://dl-ssl.google.com/android/eclipse/
Click OK
Note: If you have trouble acquiring the plugin, try using "http" in the Location URL, instead of "https" (https is preferred for security reasons).
In the Available Software dialog, select the checkbox next to Developer Tools and click Next.
In the next window, you'll see a list of the tools to be downloaded. Click Next.
Read and accept the license agreements, then click Finish.
Note: If you get a security warning saying that the authenticity or validity of the software can't be established, click OK.
When the installation completes, restart Eclipse.
You can also read more here http://developer.android.com/sdk/eclipse-adt.html
It looks to me like you are trying to install the plugin on a base Eclipse system that is too old to support it. Check the prerequisites / dependencies listed in the documentation for the specific version of the plugin that you are trying to install.
It is also possible that there is a dependency conflict with another plugin that you've installed previously.
The simple solution is to start with a clean, up-to-date Eclipse base install (with no 3rd party plugins), and add the Android plugin to that. Then add the other plugins, if you want to take the risk.
In my experience, it is a good idea to create a backup copy of your Eclipse installation before you start adding plugins ... just in case something goes wrong. And take notes of what plugins / versions you are install from where, in case you need to repeat the process in the future.