How to use Subversion with Eclipse 84
An anonymous reader writes "From the beginning, Eclipse included tight integration with the Concurrent Versions System (CVS) in order to provide access to change-management capabilities. Now, many projects -- notably those run by the Apache Software Foundation -- are using a different change-management system: Subversion. This article demonstrates how to add Subversion support to Eclipse and how to perform basic version-control activities from the IDE."
Re:I'll stick with eclipse, thanks. (Score:2)
A friend of mine used to con
Re:I'll stick with eclipse, thanks. (Score:2)
Not 500 bucks if you time it right. (Score:1)
Personally, I think it's well worth the money. I've tried Eclipse, and Idea seems a lot more streamlined and less awkward.
Re:Uh, thanks... (Score:1)
Oh, wait. Java only? Nevermind, I'll stick with Eclipse.
Why in the IDE? (Score:1)
Re:Why in the IDE? (Score:3, Insightful)
Re:Why in the IDE? (Score:4, Insightful)
Whether or not an IDE is a good idea is a seperate question all together. Maybe they are, maybe they aren't, maybe they only are for some people or situations. But if you are making one, it makes sense to make a good one.
Re:Why in the IDE? (Score:1)
Re:Why in the IDE? (Score:2)
Re:Why in the IDE? (Score:5, Funny)
Personally, I think it's much easier to use pen and paper, an abacus and a filing cabinet.
Re:Why in the IDE? (Score:1, Funny)
Re:Why in the IDE? (Score:2)
Re:Why in the IDE? (Score:2)
You laugh, but just how much easier is it to click a button in a GUI or type a keyboard shortcut as compared to clicking up-arrow+Enter to re-invoke make on the command line?
IDE's are productivity enhancers but they are often overrated. Programmers need to think more about what makes a development environment productive. Hand waving about buttons and "integration" doesn't cut it.
---
Don't be a programmer-bureaucrat; someone who substitutes marketing buzzwords and software bloat for verifiable improvem
Re:Why in the IDE? (Score:1)
Re:Why in the IDE? (Score:2)
If this plugin can act as a good svn client, without being to tightly coupled to eclipse projects, then I'd be glad to use it.
Re:Why in the IDE? (Score:1)
Re:Why in the IDE? (Score:2)
Huh?
I was asking a question based on previous experience, not slamming subeclipse.
SVN for eclipse doesent put any dependence on you using an eclipse project. In fact the plugin couldnt be more general purpose. I've used it for a year now.
Cool. That's the info I was looking for. I'll give it a shot and see if I like it better than smartsvn.
Re:Why in the IDE? (Score:2)
It's all about changing focus. Modality. (Score:3, Informative)
IMO, the reason it's desirable is because a separate interface for source control changes your focus. I haven't seen any version control software that is really well integrated. Ideally, vcs (small-caps, version control software) should be invisible -- running in the background, checking out files as you need them, saving revisions with each change, maybe version stamping with each day/build/successful test pass/etc., and onl
Re:It's all about changing focus. Modality. (Score:3, Insightful)
I have to strongly disagree with this. Changes should only be checked in when the developer decides they're ready, not every time you experimentally change some mundane detail. CVS
Re:It's all about changing focus. Modality. (Score:1)
That was a scheme that I really liked (way back when), until the BOFH set a system-wide limit of three versions...
Re:It's all about changing focus. Modality. (Score:2)
It all depends upon how you manage development. If you have a task that is going to require a significant ongoing effort (ie: more than a day or so) or that is going to require communication amongst multiple developers, or which will be undergoing lots of change (ie: you're doing research not development) then it makes sense to create a branch to manage the effort, and then merge the results of that effort back into the trunk when it's ready.
Note: I'm not defending automatic check-in, I'm suggesting that
Re:It's all about changing focus. Modality. (Score:1)
Re:It's all about changing focus. Modality. (Score:3, Informative)
Re:It's all about changing focus. Modality. (Score:2)
Which would make version control unwieldly, unless you tagged every "real" check in.
VMS (Score:3, Interesting)
If any ot
Re:VMS (Score:1)
More seriously, they're going to open the source to ClearCase's MVFS, which might be an interesting starting point. Depending on how it's implemented, you might be able to plug a different version control system into it.
Re:It's all about changing focus. Modality. (Score:2)
Hey, 1989 called. They want their version control paradigm back.
(Sorry, couldn't resist.)
Idea implements this in a smart way (Score:2)
Re:Why in the IDE? (Score:3, Insightful)
Since fixing integration problems with incompatible changes can play hell with your schedule, the wisest thing is to force yourself to do it every single day. If anything, source control isn't bound tightly enough with IDEs.
Re:Why in the IDE? (Score:2)
Re:Why in the IDE? (Score:3, Informative)
Two, for refactorings. Modern IDEs have support for many common refactorings tasks, allowing you to (for example) pull out new sub-methods and be confident in the knowledge you haven't effected the rest of the program. Ideally, a version-control aware IDE
Re:Why in the IDE? (Score:5, Informative)
Re:Why in the IDE? (Score:1)
Re:Why in the IDE? (Score:2)
I gave my developers a pretty easy-to-use setup for creating and using svn repositories, and taught them how to use tortoisesvn (this was
Then I taught them how to use subclipse about a month later, and now they generally find the reposito
Re:Why in the IDE? (Score:2)
Yes, I think. While I don't routinely program much lately I have been testing some of Eclipse integration with CVS. It's very nice. Because Eclipse understand the source code structure it can do things like showing the difference in code structure, like which metods were modified compared to the remote version. It can show w
Re:Why in the IDE? (Score:1)
While I agree that the IDE should not be the only way to access version control (it's blasphemous, I know, but I don't use an IDE for everything), it is helpful to have access from the IDE when I am working it - no need to task-switch.
The one thing that I find really helpful in the Eclipse integration with subversion is the display of diffs of Java source files. The diff is displayed in terms of language artifacts (such as showing that a particular method was added or modified), instead of simply simply
Thats Easy! ... (Score:2, Funny)
This is particularly effective in places relying on visual recognition algorithms using only the visual spectrum in ambient light conditions.
Unfortunately it might take several tried to get the timing right, and rebuilding a system just to have another go-around can be too time comsuming for most practitioners.
Eclipse 3.2 and Mac OS X/Linux (Score:4, Informative)
Re:Eclipse 3.2 and Mac OS X/Linux (Score:2)
Re:Eclipse 3.2 and Mac OS X/Linux (Score:1)
it's another dependency waiting to break.
In the subclipse preference you can check the "Native Java SVN" support.
It's not on by default, but has worked for my for several months.
(I do eclipse/java development for work, I should know
Excellent article (Score:5, Informative)
I've been working with Subversion, especially from within Eclipse using the Subclipse plugin. I had earlier experience with the CVS plugin that comes with Eclipse. This is with Eclipse 3.1.1, Subclipse 3.0.1 and Subversion server version "SVN/1.1.4".
Some bad differences:
Some differences I'm neutral about:
Good things:
Re:Excellent article (Score:2)
You may want to remove Subclipse and try Subversive [polarion.org]. It's free, and I've found it to be more reliable and full-featured than the Subclipse plugin. Check the FAQ before using for some info on migrating, if you choose to.
Re:Excellent article (Score:2)
That's a Subversion-ism - Subversion requires you do that via the command line whenever a file has conflicts, so Subclipse requires you do it via the GUI.
Re:Excellent article (Score:1)
-br
Re:Excellent article (Score:2)
Subclipse does support moving files in exactly the same way that Subversion handles moving files - copying the original (the history will remain attached) and then deleting the old copy.
Check out the SVN manual and look up the "svn move" command. It says:
If you check the SVN console, you'll see it does indeed make the copy followed by the delete.
Re:Excellent article (Score:1)
I switched back to IntelliJ which had a much more functional plugin. A few months later they added official support for SVN that was even better than the plugin. I don't regret the switch back at all. They even give free licenses to opensource projects.
Re:Excellent article (Score:2)
Actually, I think this is more something with eclipse or the plugin than subversion itself. The command line tools seem quite fa
Re:Subversion is not necessarily for Unix develope (Score:4, Insightful)
But it does support versioning the symlink itself (per the FAQ). Do you really want to store multiple copies of the symlink's source?
Re:Subversion is not necessarily for Unix develope (Score:1)
Re:Subversion is not necessarily for Unix develope (Score:3, Informative)
Subversion FAQ about Symbolic Links [tigris.org]:
Re:Subversion Sucks. (Score:4, Insightful)
He said he read the entire manual and still couldn't figure out the most basic of SVN operations? His reading comprehension skills must be so handicapped that I find it difficult to believe he managed to get a wordpress blog running. I downloaded, compiled, and installed subversion without reading the manual and then skimmed over the documentation to get it running. Can't figure out what it means? WTF? Either this guy is from Windows where you don't deal with permissions because you're always an administrator or he has absolutely no business setting up a server of any kind. I got that same error the first time I setup subversion through the Apache module. I immediately said "Oops, forgot to give the apache user write access to that directory, duh." So sorry that every program doesn't have a 2,000 page section in its manual covering the basics of its host operating system.
I've never used either of those repository management programs he speaks of since they are completely unnecessary given how easy it is to manage an FSFS based Subversion repository, but I'm going to go out on a limb here and say they'll work perfectly for every other user.
Actually it is that simple. That command has never failed to create a repository when I used it, and it was a simple matter of double checking the permissions afterwards and are of course easily fixed with a recursive chmod. What are some normal defaults? What do the authors recommend? I thought you read the manual asshole: The shockingly labeled "Choosing a Repository Layout" section [red-bean.com]. What should the permissions be? Umm, maybe the most restrictive ones necessary for operation, like they are or should be for every program in existence. If you're running it through the Apache module and want to commit changes and therefore write to the filesystem, perhaps the user Apache runs as needs, oh I don't know, write permissions.
Subversion has worked flawlessly and exactly according to the published documentation in every single instance I have used it. The only problems that have ever occurred in relation to it were of my own mistakes (not giving the apache user access, etc.). Given that I find it very hard to believe that someone able to comprehend a revision control system could fail so completely at such a simple task, I find it more likely that this asshole just hates Subversion because it's different and is/becoming more popular than his system of choice.
At least I'll know not to believe a single word from Sebastien Reid if I'm ever linked to his "tech blog" again.
Re:Subversion Sucks. (Score:2)
Re:Subversion Sucks. (Score:2)
Re:Subversion Sucks. (Score:1)
Re:Subversion Sucks. (Score:2)
Error/exception reporting is a bit of an Achilles heel for software in general though, not just OSS development tools.
Subversive is even better! (Score:2)
Re:Subversive is even better! (Score:2)
Another important point - Polarion (the authors) recently submitted a proposal to make subversive a standard project under eclipse.org
http://www.eclipse.org/proposals/subversive/ [eclipse.org]
Transitioned? (Score:2)
Transitioned? Sounds like you've contracted a pretty severe case of management-speak. Been leveraging one too many paradigm-shifting synergies, perhaps? The word you're looking for is "switched". As an antidote, I recommend playing Bullshit Bingo [bullshitbingo.net] at your next meeting.
But thanks for the link to Subversive! :)
Why... (Score:1)
Re:Why... (Score:1)
Re:Why... (Score:2)
An post like this is valuable because I learned (through the comments) that there are 2 add-ins for Eclipse that support Subversion. Which is more information then I had yesterday. And I get a few opinions mixed in as to which of the 2 add-ins works better. I wish we'd see more discussions of what tools and techniques are in use.
(It just so happens that we're
Re:Why... (Score:2)
Re:Why... (Score:2)
(That is, I have no idea how/why they choose to post things where they do.)
subclipse still has some way to go (Score:1)
[OT] Interfacing VSTS From Eclipse and beyond (Score:1)
As much as I aim to avoid MS, it dominates my organisation, and unfortunately the rest of the world. An expensive commercial plug-in from Teamprise [teamprise.com] was available. So this got me looking around and I found that Visual Studio Team System Foundation Server exposed a soap service for interacting with its r
SVN SSH Tunneling Information (Score:1)