In my case I zipped the svn directory, because. Configuration and setup files should be regenerated by the developer when setting up a new project. To get an exact copy onto the new server, zip all repositories at once. On the other hand, anything that isn't shared across the dev team should be left out of the repository.įurther experience has taught me that the only things that should go into source control are the actual source files. If certain plugins are universal and have config files of their own, go ahead and check those in as well. classpath files so that a new developer will be able to checkout and build immediately. If Eclipse is the standard IDE, go ahead and check in the. I'd recommend checking in whatever artifacts are universal across the development team. 10/24/19 Joe Silver, SmartSVN Support 4 Files pane post commit, scroll/selection issue I may. The last question about which artifacts to check into SVN is a matter of taste. SmartGit may require a connection to the repository when performing operations related to the omitted files. SmartSVN is a SVN GUI which ships with its own SVN binaries that cant be used outside SmartSVN. You'll be able to have projects checked out on development branches while others are on the trunk, you can revert changes to one project while leaving another alone and so forth. You'll be able to check out individual projects into the workspace without having to checkout the entire codebase. What this does for you is give you the flexibility to lay out your workspace completely separate from how your repository is structured. I'd recommend each Eclipse project have its own SVN project, so that instead of having They may end up looking similar, but that shouldn't imply that they're actually the same. The SVN layout should be separate from how your workspace is defined. You can create as many workspaces as you want for specific purposes you could even import projects in one workspace into another if you had reason to do so. Project files can (and usually do) live in the workspace, but as you know, they can be imported from an external source-the import is just a logical link. I tend to notice it when doing commits, but. I may have been wrong about the nature of this issue. Files pane post commit, scroll/selection issue. The workspace is really just where Eclipse stores a bunch of settings. SmartSVN is a SVN GUI which ships with its own SVN binaries that cant be used outside SmartSVN. Workspaces and repositories shouldn't be related.
0 Comments
Leave a Reply. |