I just made a clean install, as I do every year, of my linux system (ubuntu) on my notebook.
I just wanted to open-up eclipse from my (old) workspace, where all my code from the past 12 months is - but eclipse doesn't show a single package!
My assumption is that I used an older version of eclipse up until yesterday before the clean install, and that the version I installed today is newer, thereby doesn't recognize my worksapce(s!). Is this assumption correct? if so, Does anyone know how I can figure out which version of Eclipse I was using when working on the old Workspace, so that I can download that exact same version again?
The absolut worst-case scenario would be to c/p all classes and packages manually into the new eclipse, but it's over a 1000 classes - so that might be too time-consumming.
An help would be greatly appreciated, since there actually are 2 projects from work in those workspaces... ^^
Well, after Downloading Eclipse Mars, I found a solution. Although switching workspaces, or even importing the old workspaces didn't work, I found out that if I started eclipse from the old workspace, even though package explorer would stay empty, it would suffice to define a new java project with the exact same name of one of the projects inside the old workspace, for eclipse to instantly load-up the docs contents.
This not as much a solution, then a work-around... but still, fixed the problem!
Related
I'm developing an eclipse plugin and in order to test it I have to install it into my eclipse application regularly. However as I dont't want to change the version of my plugin every time I want to test a new feature I always uninstalled the plugin from within eclipse and afterwards I'd go to the eclipse folder and delete my plugin out of the plugins folder (and delete the respective entries in the eclipse XML-files).
That worked great in windows but I have recently switched to Linux (Mint) and I just found out that my plugin is no longer located in the plugins folder inside the eclipse program directory. Therefore I can't really delete the old plugin whcih then prevents the new version of the plugin from installing properly.
Does anyone have an idea about where eclipse copies the installed plugin or a differerent approch to actually completely uninstall (delete) an installed eclipse plugin?
Okay after searching through my whole filesystem I found it out myself.
Eclipse has a hidden folder in the home directory named .eclipse in which each installed eclipse version has it's sub-directory and in there there is also a plugins and a features folder that then contain the externally installed plugins and features.
It also contains the corresponding artifacts.xml.
I'm not sure whether this behaviour is specific to the Linux Mint OS or rather a new "feature" of Eclipse Neon but if anyone is having the same problem that's were I found it.
Help -> Installation Detail.
Then click the plugin you want removed then press "Uninstall...".
Note: there is a "Plug-ins" tab in the Installation Detail dialog. This is misleading; you are not to click it.
Ps. It might be easier to test the plugin, during development, on a run-time workbench.
After this huge mess from one AndroidStudio update, am cleaning everything and starting from scratch.
I'd like to ask if anyone knows if I should go with specific versions of Java.
But first my headache, although I just cleaned my computer of AndroidStudio.
I have Win 10 64 bit
HAD AndroidStudio 1.51 (it said it was JRE:1.7.0_79-b15 amd64)
After the update I had a "Unsupported major.minor version 52.0" error
Following some posts I upgraded the Java on my machine.
First "1.8.0_74" but AndroidStudio couldn't find the JDK directory, so I installed "1.8.0_73" and AndroidStudio found the JDK directory. But then I started getting rendering errors but with Rendering Problems Exception raised during
rendering: com.android.ide.common.rendering.api.LayoutlibCallback.getXmlFileParser(Ljava/lang/String;)Lorg/xmlpull/v1/XmlPullParser;
Anyway, that's it. This has become such a tragedy that I would rather start from scratch, but if anyone could point me as to the proper (steps) of which way I should go, I would really appreciate it.
Thanks ahead,
Sergio
I met this issue when I updated the api android 23 N (preview). In xml editor, change the Api to render into Api 23 android 6.0 and Autimatically Pick best.This would solve the problem.
refer: link
Yes.. i also faced same problem,I have resolved with changing the version to api 23.generally it will take best/latest version ,in my case its set to N preview.
I have the following odd problem:
I am working on a jdt feature. The ant script that generates the jars, signs them, etc, has worked like a charm for months.
I downloaded Mars, installed the feature successfully once(fully functional plugin). I had to make some changes, regenerated the jars and all hell broke loose.
Suddenly the icons were not in the path, tried to reinstall ide from scratch several times and now the feature fails to install silently.
After the signature verification dialogs, it silently fails. The plugins and features dirs have the installed components but the plugin doesn't load at all.
I deleted .eclipse and .p2 several times to no avail.
Clue?
Thanks in advance!
I have just upgraded to SVN 1.7.1 and I have had nothing but problems trying to get my netbeans and everything else to work with it. I have tried 'svn upgrade' but I get an error which is as follows:
C:\wamp\Projects>svn upgrade BMPortal
svn: E155019: Can't upgrade 'C:\wamp\Projects\BMPortal' as it is not a
pre-1.7 working copy directory
svn: E150000: Missing default entry
Could anyone suggest a way to fix this. The reason why I am trying to upgrade is because my netbeans says:
The Path 'C:\wamp\Projects\BMPortal' appears to be part of a
Subversion 1.7 or greater working copy. Please upgrade your Subversion
client to use this working copy.
As I have upgraded my SVN Client to 1.7, I don't know why it is still moaning at me.
Just FYI:
The SVN Server is on an Arch Linux box running UberSVN.
The client (my computer) is Windows 7 64bit.
I actually had the very same problem (or at least the same error message!).
After trying everything you have said earlier and not getting any results, I realise that I had copied some files to the project that contains svn files from an older (1.6) version. I delete the 1.6 folders and the everything worked fine again.
I hope this could help some other people too!
Best regards,
Andrés
Your Netbeans installation seems to use another SVN-Client as the one when you type svn on the console.
So you have to upgrade your Netbeans-Subversion plugin too.
Sorry to waste your time guys, I have finally found a work around for this, http://netbeans.org/projects/versioncontrol/pages/Subversion1_7
But thanks again all the same! It's much appreciated!
SVN v1.7.0 and above uses a new working copy file format, so you need to upgrade your working copy to the new format. If you right-click the folder in Windows Explorer, the TortoiseSVN context menu items should show only "SVN Upgrade working copy" - click that to upgrade it.
Warning: If you use any other SVN apps as well as TortoiseSVN on the same PC, they may not work with the new working copy file format.
It's worth upgrading in my opinion though - must faster, better merging, better dialogs and error reporting, etc!
I don't want to disable IntelliSense, but I don't see any other solution.
I have Visual C++ v10.0.30319.1, Max Cached Translation Units = 2. But still, dozens of vcpkgsrv.exe processes are spanned, consuming lots of memory (and rendering the computer unusable). Windows 7 Pro.
Any solution that you know of? Thanks.
Tools > Extension manager > installed extensions > all
Remove all the packages that are making problems like NuGet package in my case which eats all the memory... unistaling it here and restaring VS solved the problem, no need to reinstall whole windows.
Make sure you unistall dependencies first, dependencies are shown when you atempt to uninstall a package.
NOTE: if you don't uninstall dependencies the package won't be removed from the system and you'll probably have to reinstall VS or even whole windows.
EDIT:
Old solutions and projects must be deleted from the system, which means that you'll copy your .cpp and .h files and create new project because old projects may bring the problem back. I figured this out when I opened old projects and the problem was back.
After making new projects from old files everyting works as expected.