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
Related
I was having trouble getting my eclipse set up for a new project, so I copied another project over and deleted the existing files.
However the commit history is saved for all of the old files. Where do I go to delete this commit history?
Using Eclipse Neon 3
Right-click on the project, Team -> Disconnect. This will completely remove any revision information.
To create a repo with the contents of a fresh project, do the above, then close eclipse and via the command line in a terminal execute git init in that project's top folder. Open eclipse and the project is in a fresh repo without any history.
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 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.
In my python/pydev project home directory, eclipse create 3 files/directory :
.settings
.project
.pydevproject
As I do not want to share these files, I set a svn:ignore flag on the home project directory with these 3 files/directory specified in it.
It works well for .projet and .pydevproject, but not for .settings :
From time to time, .settings reappears into the "team synchronize perpective" as to be synchronized/committed into the svn repository.
How can I get the eclipse '.settings' definitively ignored during svn commit in eclipse gui ?
Do you have checked in .settings before adding it to ignored? If so, you should remove it from svn (not the working copy of cause).
If the .settings folder was previously under SVN (i.e. commited) then you should remove it from you SVN first.
If you still want to keep it in your working copy, you can do:
svn remove .settings --keep-local
in command line, and do svn ls (if you see this folder listed, you haven't removed it from SVN!!!)
If you already removed it and still have a problem you can try one of 2 things:
1. Deleting the folder manually (assuming no complex\unique settings were made)
and letting Eclipse recreate it
2. Deleting only the inner folder `.svn` (only the one inside .settings),
and then running svn cleanup (Team -> Cleanup)
The first one is preferred, since it is never the best idea to mess around with SVN's files.
You can (and should) exit eclipse, back this folder up, and update your working copy before this process.
if you have installed subversive you should also install the "subversive svn jdt ignore extensions".
you will find it here:
help > install new software ...
select your eclipse download site. in my case its "Helios - http://download.eclipse.org/releases/helios"
you'll find it under collaboration > Subversive SVN JDT Ignore Extensions (optional) (Incubation)
That sounds you have sometimes added this folder under version control and checked it it. You need to first removed it (svn rm via command line or via TortoiseSVN on windows) and do a commit. This needs to be done outside from Eclipse. After you changed that you can start Eclipse again.
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.