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!
Related
I recently upgraded to TortoiseSVN 1.8.10 and I no longer have the option to merge. Has anyone else ever experienced this?
You right-clicked something that is not a SVN working copy, but a plain old folder. Try with an existing working copy, or make one first.
Latest version of TortoiseSVN as of this moment is 1.14.1. If you are positive that you right-clicked a working copy, one possible reason would be that you downgraded TortoiseSVN instead of upgrading, and the old version does not recognize a working copy made in a more recent version.
I installed Web2py on my machine. When I click web2py.exe, a console appears for a second and disappears. Nothing more than that. What must be missing?
As per different blog post, the latest web2py version is broken. You can download an older version from the the for the time being. For my case, I am now started with a older version.
Download older version from here
It seems to be broken. However, you can download the source and run it like this:
python web2py.py
There's a discussion mentioning the problem on the web2py group and Nico Zanferrari has a fix in his repository.
I checked every thread related to that error. But I couldn't find the appropriate answer. I have additional error too. Check out the screenshots.
Posts I came across recommending fixing JDK pathing issues through "Switch IDE book JDK..." or "Project Structure".
For me, in Android Studio 3.0, "Project Structure" would no longer open, so I upgraded to 3.1. Afterwards, it still had the JDK version error, but now it let me open "Project Structure" from the "File" menu, where I was able to correct the JDK, SDK, and NDK locations and versions.
There were still several build errors after that, but clicking the recommended fix in the build output window eventually installed everything I needed. Once it managed to synchronize correctly, it also upgraded Gradle to version 4.4. That then required new build tools and so forth.
Though instructions directly, may not help everyone, but it points to configuration corruption. So, if you cannot just upgrade to get around it, I recommend making backup copies of your Android Studio settings (generally in your user's home directory like ~/.AndroidStudioX.Y), as well as your project .idea (generally in the root of your project), then deleting the originals. If that is still not enough, purge the configurations again and reinstall Android Studio.
Note: I was going back into an old project so several warnings about deprecated features being removed in 2018 had to be dealt with.
error window
Here's what worked for me!
1. First verify that your JDK is indeed higher than JDK8
jdk version
2. Press "Ctrl+Alt+Shift+S" to open project structure
enter image description here
3. Then I selected "Use the embedded JDK"
4. Click OK and retry it.
That should solve it.
I was facing same problem, getting these two kinda errors:
SDK path should not contain white space.
Gradle sync failed. Please use JDK 8 or newer.
Solution for me was to set proper SDK path with no white space in path first and than choose JDK path. After setting path I've synced the project and tada it worked...
Thanks.
I am very experienced with eclipse, using it since its Juno days, but today i have ran into one of the strangest bugs and want to know if any of you have had this bug and if you may have an answer as to how to fix it. (Or at least a work-around to getting my favorite IDE working again).
I recently updated to Ubuntu 16.04 (Xenial) and it seems nothing wants to work like it did when i had Wiley, namely eclipse. I used the installer to download the IDE and launched it and i got a strange issue where the IDE would load and ask for a workspace, but would then show a dialog box that is using the screen buffer as its data.
Screenshot with strange eclipse launch
I then thought that it may be an issue with the downloaded file (Corruption or something) so i downloaded the tar from eclipse.org directly. I extracted the tar and launched the eclipse executable and it loaded up and asked for a workspace again and began to launch, and finally it came up, the same old back buffered box.
So i got the idea to run it from the console and got this output, but i have no idea what it means. I saw no stack traces so im sure its fine (Again it may be a GTK error, so any ubuntu people this is where you come in)
Console Run with the same problem
I started to think it was my java version (Oracle JDK 9 for Linux)that was the problem so i did a test compile of the hello world program and everything was fine, it all worked.
(Would add screen shots but im new here so i dont have enough reputation to do so :( )
Any idea what it might be? Any help would be great!
I found the problem, i installed the latest version of java in the apt repository. This version was JDK9 which Eclipse does not support (At least not until Eclipse Oxygen). I purged the computerof JDK9 and installed JDK8 and everything worked fine!
Moral of the story, don't use JDK9 on Neon
I am running a dual boot windows 10 and Ubuntu 16.04, I have similar issue where I can see all the file menu and the eclipse launched on the tool bar, I have selected the application and used ctrl+WindowsKey+left,right to split the application to half of my screen and then magically it appeared,Then I adjusted to fit to my screen.
Would a fresh install work? I didn't have any issues. Perhaps ask this on ask ubuntu, too.
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!