I am using team svn plugin in my eclipse helios pydev project.I deleted a repository file in eclipse and then committed the changes and all went well. The file got removed from repository fine.
Lets say package structure is like this in repo
dev/
folderA/
folderB/
C.py
In eclipse dev is the project name.
I deleted C.py from eclipse and commited using svn team commit option.
It worked fine.
Now when I try to compare folderA with repo folderA, Eclipse try to compare C.py from the revision which obviously is not there and does not allow compare to work.
Somehow eclipse has that file in its memory.
How can I make eclipse know that file is deleted and is not supposed to be there in first place?
it seems that was just a synchronisation problem as after updating from the repo the problem was solved.
Related
I have a fresh workspace (empty folder) on a Windows Share (i.e. \\myServer\myWorkspace). I start eclipse on this workspace. Until now everything works fine.
Now I do a "Import" - "Checkout Project from SVN" and import one of my projects (using the sublipse plugin for eclipse).
The project is checked out and appears in the project explorer. BUT the SVN Version information is completely wrong, showing the date 01.01.1970:
No commit or update is possible.
When I put the workspace on a local disk like C:\MyWorkspace, the checkout is working fine.
How can I checkout SVN project to a workspace on a Windows Share?
Subclipse gets all of its info from SVN API. I seem to recall there is a bug in SVN when the root of the share is a working copy which sounds like it could be the case for you. If it is, try creating a folder on the share for your working copy and move it into that folder to see if it makes a difference.
I have accidentally deleted .svn directory from my maven project. Now when I started eclipse the projected shows no connections to svn repository. I am not able to assign the svn url to the project.
How can I assign the repository url to the maven project in eclipse to be able to synchronize.
First: make a backup. (zip the current folder)
Then: within eclipse you should be able to simply share the project (again) and select the SVN repository. Eclipse usually syncs the sources and the repository. Usually nothing gets lost in the process but better be safe and make a backup.
For maven no action should be required. There is the scm section in the pom.xml but that probably did not change. As long as no plugin reads the SVN revision number or you do a release locally maven will be fine.
I'm in an annoying situation with Eclipse and I want to know if there's a better way I can setup my project / git repository to avoid having to constantly manually fix my project to compile.
Background:
While developing our Android App we had a version 1.1.x live and in git.
We're now working on version 1.2.x in development, which is a fork of 1.1.x. At the same time, we have to switch back to the 1.1.x line to fix bugs in what's currently live.
The issue is that the 1.2.x line has a new Library Project in it, which is only present in the 1.2.x branch. I have to switch between both branches a lot to do development for both, but Eclipse isn't handling it very well.
When switching to the 1.1.x branch:
Problem: Eclipse complains e.g. "AndroidManifest.xml file missing!", because the folder for the library project no longer exists on the file system (git has deleted it - remember it's not in the 1.1.x branch).
Current Fix: Click on the folder in Package Explorer, delete it.
When switching to the 1.2.x branch:
Problem: I deleted the folder for the 1.1.x branch, so now that dependency is missing when Eclipse goes to build the project, and there's a bunch of build errors. To be clear, project.properties lists the dependency and it's in the Build Path - but (I don't know the terminology) the Eclipse whatever is missing from the workspace, and the dependency is listed as missing (shows as a red X under Project Properties > Android > Library).
Current Fix: Because of two different Eclipse bugs (Eclipse "Invalid Project Description" when creating new project from existing source, Some projects cannot be imported because they already exist in the workspace error in Eclipse), I have to Import > General > Existing ..., Browse... for the root directory, uncheck Copy, click refresh, and finally select the project and click Finish.
What can I do so that this process is automated when jumping across branches?
If everybody is working in Eclipse then I you can commit your eclipse resources with your project
.project
.classpath
.settings/*
You might be ignoring these files in your .gitgignore, so simply remove them. This will not help for past commits unless you are willing to do a rebase with edit or filter-branch to add these files retroactively.
I had some nice eclipse run configurations I had created while working on a branch in SVN. I then merged these changes back into the trunk, and now my eclipse run configurations are gone. Why? My eclipse configuration directory is totally separate from my svn directory.
Try saving your run configurations as "shared". They will be saved as .launch files that you could add to your SVN repository to make sure they don't get lost again.
Example here
I have an eclipse project on my hard disk, which is a fairly recent check out from an SVN repository. I've imported this project into my Eclipse workspace, and now want to associate it with the SVN repository.
How do I do this? The only options I seem to have under Right-click -> Team is "Share Project", which only seems to allow me to do an initial import.
Edit: Motivation - It's a largish repository, and I don't really want to have to import the whole thing over the network.
Edit 2: There are (for some reason) no .svn dirs in the project. So maybe a fresh import from svn is the only option
Team->Share project is exactly what you need to do. Select SVN from the list, then click "Next". Subclipse will notice the presence of .svn directories that will ask you to confirm that the information is correct, and associate the project with subclipse.
I just wanted to add that if you don't see Team -> Share project, it's likely you have to remove the project from the workspace before importing it back in. This is what happened to me, and I had to remove and readd it to the workspace for it to fix itself. (This happened when moving from dramatically different Eclipse versions + plugins using the same workspace.)
subclipse not showing "share project" option on project context menu in eclipse
I'm asked this question very frequently, if it's smart to use "Share project..." if a eclipse project has been disconnected from it SVN counterpart in the repository. So, I append my answer to this thread.
The SVN-Team option "Share project ..." is totally fine for projects that exist in SVN and in your Eclipse workspace, even if the Eclipse project is missing the hidden .svn configuration. You can still connect them. Eclipse SVN-implementation (Subclipse/Subversive) will verify if the provided SVN http(s) source is populated. If yes, all existing files will be copied and linked (checked out in SVN terms) to your very personal Eclipse workspace.
Word of caution:
Do a backup if you depend on you local files. The SVN implementation may vary its behaviour with every release.
If you have multiple projects encapsulated within each other, make sure you point the SVN path to the correct local path.
regards,
Feder
I came across the same issue. I checked out using Tortoise client and then tried to import the projects in Eclipse using import wizard. Eclipse did not recognize the svn location. I tried share option as mentioned in the above posts and it tried to commit these projects into SVN. But my issue was a version mismatch. I selected svn 1.8 version in eclipse (I was using 1.7 in eclipse and 1.8.8 in tortoise) and then re imported the projects. It resolved with no issues.
I am using Tortoise SVN client. You can alternativley check out the required project from SVN in some folder. You can see a .SVN folder inside the project. Copy the .SVN folder into the workspace folder. Now remove the project from eclipse and import the same again into eclipse. You can see now the project is now associated with svn
In case of SVN servers you have to creating a central repository with all projects. The contents of the repository can be uploaded with the Team/Share command; in case of the Subversive client it automatically runs a commit after the import, so you can upload your files.
This step cannot be circumvented in any way using a centralized version management system such as SVN.
Try this- Close the project then open it. It links with svn automatically,if project was checked out from valid svn path.