Is it possible to leverage eclipses built-in local history to create and save versions. I find local history very useful, but if I could restore the whole project to a previous state that would be even better. I've considered using version management, but it seems unnecessary as I am the only person working on my project. And I could really benefit from the ability to name my (local history) versions instead of having to go by date.
Thanks,
Lemiant
You're going through a lot of hassle just to avoid version control. Instead! Use a local version of subversion for all your version control needs.
You do not need to host a server. It will use the filesystem only! Use subclipse or subversive to integrate into eclipse.
A tutorial how to set it up(takes less than 5 minutes):
http://vincenthomedev.wordpress.com/2007/10/15/setup-svn-local-repository-step-by-step/
Related
I am doing a project in my spare time, and I need version control. Mainly I need some kind of sync that keeps remote / local files synced up since I make changes both on the server and locally.
Environment is Windows 8, 64bit, main dev tool is Dreamweaver, and the servers are on the host at the moment (although I am thinking for setting up a local db and server).
I don't want anything fancy, or complicated and only this very basic functionality is needed. Just for it to keep track of whether the server version and the local version is most recent, possible warn me if I am about to make a version control mistake.
You say that you need "some kind of sync that keeps remote / local files synced up" with simple workflow. Take a closer look at Apache Subversion (SVN) then; SVN is a storage and a time machine for your sources and is a great solution to organize your code and development process. Read SVNBook!
Adobe Dreamweaver supports SVN out-of-the-box, BTW. There is a good article series about using Dreamweaver with SVN:
Using Subversion with Dreamweaver CS5 – Part 1: Introducing Subversion,
Using Subversion with Adobe Dreamweaver CS5 – Part 2: Configuring Dreamweaver to use Subversion.
I work with Tortoise SVN for versioning the code. I have the last version installed (1.7.10).
I created the local repositories using this tool.
Recently I installed the last version of EasyEclipse for PHP (1.2.2.2), when I try to connect to the Repositories I get this error:
Unsupported FS
format svn: Expected FS format '2'; found format '4'
How can I specify the correct FS format in Tortoise or in Eclipse?
Really you can't.
And I'll suggest don't use EasyEclipse at all, because it expect ancient format of repo (2 is "pre-1.5"), while more recent versions (of repo-formats) have serious improvements in different areas
When sharing a working copy between multiple Subversion clients, all must be at the same major.minor version number. EasyEclipse is looking for a working copy that has been created with a Subversion client earlier than 1.7, because it apparently bundles an older version of the libraries.
I know nothing about EasyEclipse but looking at their "news" page, it appears to be abandoned. You'll either need to roll back TortoiseSVN to a release of similar vintage (and dump/reload your repository, since it sounds like you're not using a Subversion server), or upgrade your PHP IDE to something that's actively being maintained and up to speed with current releases.
I want to roll back my Google Plugin for Eclipse to a previous version. How can I accomplish that?
Use Help>About>Installation Details>Installation History to see your past list of installed configurations. You should be able to select one and revert to that configuration.
EDIT: update from comments
While eclipse keeps around the past configurations it may need to go to p2 repositories on the internet to download the older artifacts (and that can trip up some configuration reverts).
Unless you have a copy of the older version, you can't roll back. You can definitely get old versions of GWT, but they don't keep around old versions of GPE.
which is best sourcesafe system for iphone xcode on backup and proper check-in & check-out on codes
Regards,
sathish
it appears that you're using 'sourcesafe' as a generic term for version control.
for version control of xcode projects:
i have used cvs, subversion, and now git (also serving as a front-end for other systems).
git is my first choice (it is distributed, and quite fast).
svn (subversion) is my second choice - you may have more coworkers/projects which prefer svn, although git may also be used as a svn client.
lastly - i prefer using dedicated visual clients over xcode... xcode seems to be busy doing other things. it is usually faster to disable vc in xcode, and hop to a terminal or other client while xcode builds/debugs/updates indexes, etc.
XCode supports CVS, Perforce and SVN out of the box. Out of the three, I think SVN is the most popular choice.
Setup your project.
Delete the build folder.
Setup repository.
Import project to repo.
Checkout project from repo so you'll get a versioned copy.
Well, first - it is not called sourcesafe system, but version control - way of controlling evolution of source code and its versioning. Sourcesafe is a specific product by Microsoft.
Second - version control is data agnostic. That means you can use any system you know. The best tool is the one you know well.
That being said, there are some advantages in using specific version control systems as Subversion and Git, because those two are going to be supported in next version of Xcode (version 4).
Current Xcode (version 3) has support for Subversion, CVS and Perforce. If you are familiar with any of these, use them, but do not restrict yourself only to these. Stability of version control support in Xcode 3 is mediocre, at least with Subversion which I've used. Xcode 4 is going to be a huge improvement in this area.
Lots of developers, me included, prefer not to use integrated support for version control in Xcode (or any other developer tools), but use specific clients - like Versions for Subversion, or command-line tools for Git.
I want to comment on use of Git, which I personally use and love. It is a distributed system, and for beginners its concepts might be a bit hard to grasp. Consider the experience of your teammates when deciding to use it - for lots of teams it's better to use something more traditional like Subversion.
SmartCVS is also one of good tool which we use for co working with teammates
I like to keep my source files on a USB drive for the portability. To date I have been using Visual SourceSafe for this purpose. What is a good alternative to VSS that fulfils these criteria:
Entire database can be held on a USB "pen" drive
Code / documentation duplicated on local drives
Does not require a central server
Easy to backup and restore using standard backup tools
Integrates with Visual Studio
Has a small footprint
Easy to clean the database and keep small
Compatible with Windows XP, Vista and Vista x64
A good reference on setup would be good too.
I would use SVN (Subversion).
You can use SVN in "file" mode (w/o using the network).
combine this with tortoiseSVN, which integrates to explorer, and you have a nice little portable repository.
For Visual Studio integration, there is the commercial($49) VisualSVN (which I believe is the setup used to develop StackOverflow).
Someone also mentioned AnkhSVN which I haven't used, but some people find it less than satisfying.
Don't use SourceSafe. There's major problems with it. See this:
Article1
Article2
I'd recommend using SubVersion instead.
If you're using Windows, you can use TortoiseSVN.
If you're working on Linux or other Unix variants, try RapidSVN.
Use Subversion. The FSFS style repository will work best as older BDB ones can have issues when moved from computer to computer. With AnkhSVN you'll have full integration with Visual Studio (AnkhSVN 2.x is a source control plugin; older versions still do the job, though).
Bazaar does what you're asking for (in terms of working very well standalone), and there was a 2007 Summer of Code project to build a Visual Studio integration plugin which appears to have produced an at-least-partially-functional product.
Bazaar (and other distributed tools, such as Git, Mercurial, Darcs and the like) are ideal because you can have your repository stored in multiple places (ie. on your pen drive, but also copied up to a server on a regular basis), make changes in one or the other branch (let's say you leave your pen drive at home -- you can build changes against the copy on a remote server, upload them via WebDAV, SFTP, etc, and be able to seamlessly merge them into changes done locally to the pen drive; non-distributed solutions such as Subversion don't have that capability).
There are two common free front-ends Ankhsvn integrates into visual studio
and TortoiseSVN integrates with explorer ( my preference).
There is also sliksvn a self contained svn server for windows.
I'd recommend SubVersion as well - you can find a hosting provider who offers SVN for really cheap, this way your source code is always backed up and available, all you need to keep on your flash drive is SVN client...