I'm new to Aptana and I noticed that when uploading via FTP or checking in a project through SVN, it also uploads / checks in the .project file. I did hide this and other hidden files in the Project and App Explorers but for some reason the .project file still uploads when deploying a whole project. Any suggestions?
If you use command line SVN client (like CollabNet Subversion on Windows), go to your project folder which contains .project and .classpath file (we usually ignore both with some other IDE generated folders/files), this is the command to add a specific file to SVN ignore list:
> svn propset svn:ignore -F .project
If you use GUI SVN client (like TortoiseSVN on Windows), ignore function is usually integrated into Right-Click Menu, right click the file you want to ignored then choose TortoiseSVN -- Delete and add to ignore list).
Check out the ignore section in SVN user giude here.
Related
So, here in the company we work with svn, and our svn server only have the source folder. When I use NetBeans, it's everything ok because I can add source folders in project and will work fine in svn. But on eclipse if i do the checkout from command line and add that folder in my dynamic web project, I can't see the svn history and nothing, svnclipse just does not work on that folder.
Our structure of the projects it's something like this
Workspace
Project folder
Project1
Project configuration files
SourceCode
Packages
Project folder 2
Project2
SourceCode
I already try to make checkout using svnclipse, but he add alot of extra config files, he turns the folder in a project and the source folder is add as a link to another project, in this scenario the svnclipse quick diff does not work properly.
There is a way to use that folder as source and Svnclipse works on that ?
Sorry if my English is not so good
There is no easy way to do what you want. In Eclipse a source control provider can only be connected to the project itself. So options are:
Use another svn client like command line or TortoiseSVN.
Create a small SVN project with the Eclipse project configuration files that also use svn:externals to pull in your source folder from repository.
With option 2, you would checkout this small SVN project from some other repository using Subclipse in Eclipse, could even be a local file:// repository and then the svn:externals property would also cause your source folder to be checked out.
I'm using LiClipse which is based on Eclipse. With EGit, I pushed most of the files and directories into a GitHub repository.
However, there is one file that I can not find a way to check in to the repository: .project, the XML file.
How do I check in this file? Even manually?
Maybe you can (from a command-line git session) add a .project, but you can't from Eclispe, because Eclipse filters by default the "resource files", ie the '.*' files.
If that is the case, see "How can I get Eclipse to show .* files?".
Then, if that file isn't ignored by git, you can add it.
Or you can force the add (at least in command line: git add --force)
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 want to tell SVN in Eclipse to ignore these when I check in the code.
where is the place to go to set this ignore list:
.classpath
.project
.settings*
target
Select project > Team > Synchronize with Repository.
Then right-click on file, select "Add to svn:ignore"
Or go to Window > Preferences > Team > Ignored Resources and add the patterns there.
Make sure you ignore the file type BEFORE commiting to repository since SVN doesn't allow you to ignore a committed file or type.
You can add them as svn properties using a command line client or the TeamSynchronizing menu via the "Add to svn:ignore" sub menu.
With a svn client :
svn propset svn:ignore .classpath .
svn propset svn:ignore .project .
svn propset svn:ignore .settings* .
svn propset svn:ignore target .
Right-click the file or directory you want to exclude from version control, then choose Team > Add to svn:ignore to display the Add to svn:ignore dialog.
If you've already committed the .project and / or the .classpath files, all is not lost!
Delete the .project and / or .classpath files manually: you can use the command line, for example, or go to your project in a navigator window (not Eclipse) where you will need to show hidden files.
Refresh your project in Eclipse, and it'll give you plenty of errors.
Commit (by right-clicking your project) the fact that the files are deleted.
Then you can rebuild your project to get rid of the errors.
To check list of ignored items:
Right click on the project -> Team -> Show properties -> 'svn:ignore' item in the table
What actually happens to the file system when you do a Subclipse Share Project on an Eclipse project that was externally checked out from Subversion? All the .svn folders are already in place. I get an error when I try to Share Project the right way, and I'd rather not delete and re-checkout the projects from the SVN Repository browser.
Dunno exactly what happens within eclipse, I presume it does some funky stuff in the .metadata directory of the workspace. That said, I would recommend the following to get eclipse to learn about the svn settings of the project:
Delete the project from the workspace (keep "Delete project contents on disk" unchecked)
File > Import... > General > Existing Projects into Workspace
Browse to the folder containing the original project(s) of interest
Import the projects into your workspace
This seems to have the side effect of subclipse noticing the subversion settings when importing the "new" projects into your workspace.
The Share Project action is intended to commit the first version of a project, i.e. one with no .svn metadata in place. It will get upset if it sees .svn directories already there. As Rob wrote, the way to get that checked-out project into Eclipse is to use the import capability.
I'm not sure what version of Eclipse you are using or whether this will apply since I'm using Subversive instead of Subclipse. When I use the share project feature to commit the project into svn when I already have all of the .svn directories in place, I get a choice of like "Use current project settings" and then eclipse automatically reattaches the project svn information to the team integration. You can screw it up if you try to enter different information.