I'm using NetBeans since release 4.0 and so I'm re-using my configuration from upgrade to upgrade. Unfortunately that means, that newer default settings aren't updated, for example the URL of the plugin portal. As the old one on netbeans.org is closed now, I have to download all plugins one-by-one and to install them manually.
On https://plugins.netbeans.apache.org/ there are tons of plugins but I can't figure out, where the corresponding .gz file is, so that the IDE can load them by itself. The given "https://netbeans.apache.org/nb/plugins/15/catalog.xml.gz" contains lousy 3 modules only.
Related
So I am trying to run a google web application through eclipse, but when I run it gives me an error to please check for newest SDK version, which is 1.9.1. And sure enough Im working with 1.9.0, but I cant find any updates for GAE and it says all components are installed under help->install new software.
Ive tried downloading .zip file of 1.9.1 and extracting it to my eclipse\dropins dir but that doesnt do anything either. What do I do after Ive extracted it in to my dropins dir? And why cant I find the new version using eclipse own installation tool? Should I really be getting this error?
Try Eclipse Help -> Check for Updates instead. Sometimes the SDK detects a new version before Eclipse does, and everything synchronizes within a day or so. The SDK message is informational, not an error, so you can safely ignore it in the meantime.
In addition to what Martin suggested, you can download the SDK separately and unzip that in any separate folder. Then from your Eclipse Preferences, go to Google, App Engine SDK and select that particular version folder.
FYI - I prefer keeping the SDK versions separate from Eclipse. That way, I have the entire list of SDKs available in another folder structure and can use it across Eclipse versions too.
Is it somehow possible to manually copy the plugin from one version to the next? Basically I want to copy a plugin from Netbeans 7.3 beta 2 to Netbeans 7.3 (final release).
The plugin in question is JIRA.
Alos if someone has any other idea how to install it (can I download the plugin for previous version manually for example)
I have tried few things but non of them worked.
copy the folders under extra in netbeans dir
tried to download it from http://dlc.sun.com.edgesuite.net/netbeans/updates/7.3/uc/beta2/certified/modules/extra/ but it kept requesting additional plugins that I couldnt find. It didnt resolve dependencies by itself
Beta versions of NetBeans have a 'Plugins in Development' update center set up, which is omitted from Release build (in order to by default only provide plugins that are known to work). To add Plugins in Development update center follow these steps:
Open Plugins dialog, go to Settings tab.
Click on Add
Enter Plugins in development as a name (or whatever you choose)
Enter http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz as a URL
Click OK
Install your JIRA plugin
Another update centre you might want to set up is the one associated with Community Plug-In Portal and it's URL is: http://plugins.netbeans.org/nbpluginportal/files/nbms/pluginportal-update-center.xml
I do C++ embedded development for the NetBurner platform. They have plug-ins that customize Eclipse and in addition to a build tool-chain they add a Launch Group under the Run Configuration area. Everything was working fine under Indigo (32 bit) when I decided to install Subclipse (big mistake). As soon as the install finished I could no longer run my existing configurations successfully. When I went into the Run Configurations area I noticed the Launch Group I used to use was missing. Here is what it looked like earlier yesterday:
Here's what it looks like today:
Things I've tried
First I uninstalled the Subclipse plugins using the
Help->About->Installation Details and then selecting them one at a
time, Uninstalling and restarting after each uninstall. No change.
Then I unpacked the original Eclipse Indigo/CDT 32 bit download to a
fresh folder. Copied over the NetBurner plugins from the zip I got
from the manufacturer. No change.
Launched with different Workspaces, no change.
Launched a Galileo version, it uses older plug-ins, and it still
works.
Copied older plug-ins into Indigo, the older NetBurner launcher
shows up (but it doesn't really work with Indigo)
Removed the older plug-ins put in the newer ones, old NetBurner
launcher went away new launcher does not show up.
Tried removing the
{Workspace}.metadata.plugins\org.eclipse.debug.core.launches - no
change.
Interestingly even though launches has many .launch files that should show up under Run Configuration, nothing shows up.
One other strange (possibly relevant) thing is that icon for the NetBurner Perspective went away, now it just has <NetBurner> as the text and a generic perspective icon.
I can still cross-compile and build for the NetBurner (i.e. the build toolchain still works), it's just the ability to use run configurations that seems to be missing.
I'm out of ideas, does anyone know of some global setting that sits outside the workspace and outside the Indigo installation folder that could be causing this?
I'm running on Win 7 64 bit ultimate, I run the 32 bit version of Indigo because the 64 bit doesn't appear to work with the NetBurner plug-ins. I've also disabled the two Mylyn tasks under General->Startup and Shutdown (they seemed to cause many Permgen memory crashes). This is the same setup I had working flawlessly yesterday.
Update
I also noticed that only 3 of the 4plug-ins are showing up in the Installation Details plug-in pane. The nbeclipse.core_2.6.0.jar is in the eclipse plugin directory but not showing as loaded. So I guess I know now the problem is the plug-in isn't loading but I don't know why or how to get it to load, or what subclipse could have changed that would cause this.
I suspect that the Subclipse installation may have caused an update to some other plugin(s) that it depended on (keep in mind the transitive nature plugin dependency resolution; if you're installing plugin A and it requires a certain version of Plugin B that you don't have, Plugin B will be installed or updated to that version). In doing so, maybe the NetBurner plugin can no longer load because its declared dependencies are no longer met (ie, it depended on an earlier version and does not tolerate a later version).
You can use the OSGi Console to help determine why a plugin is not loading. Here are a couple of references that should help:
http://grep.elasticpath.com/community/techblog/blog/2010/05/27/eclipse-plugins-and-the-osgi-console
http://www.vogella.com/articles/OSGi/article.html#osgiconsole
By the way, you can not just copy plugins into an Eclipse installation and expect them to work. For several versions now, Eclipse has not supported that ability. You must use Help > Install New Software or File > Import > Install > From Existing Installation to install plugins. Ask the vendor if they have an update site to install from; like I said above, simply dropping things into Eclipse's plugins folder is not supported any more, it won't work. Other than the vendor providing an update site, the only other option is to use the dropins folder, as described here.
I am using Eclipse 3.6, and looking to update the installation to newer release, that is 3.7. Instead of downloading the whole package, can I just perform a update(distribution update)? Is there exists any way to easily achieve this?
I would not recommend that. Eclipse minor versions are more like major versions (updated once a year), so most (if not all) of the plugins are updated in the meantime. There are 2 aspects here:
The download time for all of the updated plugins may be higher than the download time for the whole bundle.
There is no guarantee that all of the plugins may be upgraded seamlessly. That means that your updated environment may not work well together.
One indication that helps is that each new eclipse release comes with new update sites. My rule of thumb is, that updates are possible with the same update site, but with a complete new version with a new update site, I always install the new release all together.
Start Eclipse; from the Help menu, choose "Check for Updates". It starts searching for updates - this may take a while, but when finished you can see a list of available updates for Eclipse (including any supported plugins that you installed). Select the update(s) you want to install and click "Next".
When I try to install Eclipse plugins, I often get an error with details like:
An error occurred while collecting
items to be installed No repository
found containing:
org.eclipse.equinox.concurrent/osgi.bundle/1.0.0.v20090520-1800
This is clearly a bug in Eclipse. The bundle I'm installing doesn't need any special version of anything, it's just a profiler plugin that works in literally any build of Eclipse 3.4. Refusing to install my plugin is not an acceptable course of action. Eclipse should stop showing this message and install the plugin.
I'm not sure exactly what error the Eclipse developers made, but I can see that the version compatibility checker is absolutely strict, and it should not be. Either it is incorrectly evaluating the required bundles, and failing as a result of its own blunder, or the version requirements of the bundles are loosely defined in a way that the version checker does not really understand.
So, is there a way to simply disable this version checker? The thing is crippling my Eclipse install. Frankly, Eclipse would be better if the thing were completely deleted from the application. We only need it to choose the correct version of existing plugins for binding OSGi services. We don't need our development tools to kibitz about whether a plugin seems proper.
Thanks in advance for any suggestions.
Byron
As mentioned in the wiki
The message indicates that the Eclipse provisioning system P2 has found meta data to install a plug-in but can not locate an artifact repository that provides the required downloads
It is suggested to remove update sites and re-add the same update sites, to trigger a refresh, but in your case, it is not your plugin update site which is involved.
There is indeed a bug (236437) with Eclipse 3.4 about "Lost artifact repositories". It has been solved in Eclipse3.5, but if you cannot use that version, there may be a workaround:
1) export the update site listing to bookmarks.xml file (Software Updates->Manage Sites->Export)
2) stop eclipse
3) remove configuration/.settings/org.eclipse.equinox.p2.*.prefs files
4) start eclipse
5) import the bookmarks.xml file (Software Updates->Manage sites->Import) that was exported in step 1
Comment #59 helped me fix my updating problem, thanks!
Though, I think maybe it was enough to just delete the configuration/.settings/org.eclipse.equinox.p2.*.prefs files as I have a feeling that the problem was already resolved before I imported the bookmarks file (things happened a bit in parallel for me here).
Note for Eclipse3.5 users:
I am seeing this in 3.5.1 when trying to install stuff from an old style update
site when I include site.xml:
http://www.perforce.com/downloads/http/p4-wsad/install/site.xml
If I remove site.xml I can install things fine.