In my project we control the plug-ins through the "Manage Configuration" possibility.
Downloaded plu-ins etc. are loaded thorugh an extension point from a file location (managed by SVN)
This has proven to be a reliable way of making sure all developers in a team share the same configuration.
I am now updating our project to Juno, and even after enabling the "Classic Update" in preferences, the menu item Help->Software Update->Manage Configuration is missing.
It also seems to be missing in the documentation for juno at http://help.eclipse.org/juno/index.jsp
Any help?
The Update Manager was deprecated a while ago, and has finally been removed in Juno (4.2). You can use the p2 director to perform command-line based installs.
There are other command line apps that can assist with mirroring features in existing update sites to a local directory that can be shared within a company or creating a composite repo that points off to multiple separate update sites (kinda one-stop-shopping) and even publishers that can take featuers and plugins without metadata and prep them for use with the p2 director.
EDIT: A quick tour of options is available here: http://pweclipse.blogspot.ca/2011/06/p2-cheatsheet.html
I've found myself in the odd position of being a TA for a software engineering class wherein I routinely have to check out each student's project from a Subversion repository. What this currently entails is manually adding around 100 repositories to Eclipse every two weeks.
All of the repository URLs are of the same form, something along the lines of domain/svn/teamXprojectY where X and Y are numbers in a given range. It would be trivial to output these URLs to a text file or something along those lines, but is there any way to automate adding these repositories to Subclipse? I've searched online as well as in the Preferences and menu options for Subclipse and can't find anything that might help me.
If anybody has any idea how to do this, it would be much appreciated. Thanks!
You can make an Eclipse "Team Project Set" file that lists all the projects you want to checkout. You then just have to import this file and it will add all the repositories and checkout out the projects.
The easiest way to see the format of the file is to take a workspace with a few sample projects checked out via Subclipse in it and do File > Export > Team Project Set and choose those projects.
You can then edit this file with any editor and later on do File > Import > Team Project Set.
If you are willing to serve your repositories via Apache, then another option is to install CollabNet Subversion Edge on your server and CollabNet Desktop in Eclipse (all free). With this combination, you just enter the URL of your Subversion Edge server into the CollabNet Sites view and all of the repositories on the server are accessible without entering their URL's.
http://www.open.collab.net/products/subversion/whatsnew.html
There are other reasons using Subversion Edge might make your life easier. The next version due in a week has a full REST API so you could automate managing users and repositories via scripts. Even without that, it gives you a full web UI to manage the server and repositories.
When I first installed the Flash Builder 4.5 trial and created a new project from existing sources which happened to be an svn repository checked out to my local web server, I had svn info including revision number and the ability to right-click to svn tools in the PHP Explorer View. At some time this disappeared in the last few weeks, now I need to go back to the folder (in Windows) containing the working copy to perform an update, commit, or to browse the log.
I have the default Zend Studio installation and then I tried to fix this by installing subclipse from http://subclipse.tigris.org/update_1.6.x, that hasn't worked either.
I have tried going thru every Preference I could think of.
I do not want to use subclipse to check-out because I want to save them to a specific path that I have in my virtual hosts file for my local Apache server.
Any thoughts on how to turn this behavior back on?
We are migrating from a Server 2000 machine to a Server 2008. I have already found great instructions for packing up my repository and moving it to the new machine.
My development tool is Eclipse. My goal is to not remove all of my projects and check them all back out. That will be a huge pain.
What is the easiest way to point Eclipse over to the new server without removing my existing projects?
The hard method looks to be running some kind of a script that edits about 9 billion CVS\Root files and updates the ip address.
Change the repo settings within Eclipse from the CVS Repositories perspective. Right-click on your repository definitions, change the settings to the new server.
When you save the settings, Eclipse will ask you to confirm that you're changing the server, and then it will update all the required metatdata files.
I've got a working copy checked out with svn; furthermore, I've created a new project in Eclipse that has the root of the working copy as the project's location. I want to be able to do stuff like compare versions from Eclipse. I have Subclipse 1.4.8, but that doesn't seem to give me what I want. Am I doing something wrong?
i have an svn working copy that also is a project in eclipse. after installing the subclipse plugin i had the same problem, the working copy was not recognized as such.
i just managed by chance to get it recognized as an svn working copy by renaming the project in question and then renaming it back to its old name. not very nice, but it did the trick :-)
There is an option when creating a new project, to use an existing source directory:
New project/ new Java Project / Create project from existing source.
Use that, tell it where your source lives, and it should automatically detect if it's a SVN working copy.
I guess this is not possible with Subclipse as it's given in its documentation that, you can only import an existing svn-managed folder under one condition, according to the doc:
"The only requirement is that your
working copy has to also be a valid
Eclipse project."
So, if you have a working copy that is not a complete eclipse project, Subclipse will not connect it to SVN.
You can right click on the root node of your project and select: Team / Share project
Then you choose SVN, let the default settings and it should work fine!
I am answering this after a long time of the question being asked. I ended up here because I was facing the same problem.
My solution was to create an empty .svn folder at the root folder of the project (in the latest version of svn client tortoise all meta-data is at the root folder). Then did an eclipse refresh and voila it did the trick. I am running subclipse core - 1.8.4.
One step that seemed to work for me, that no one has explicitly mentioned yet: I closed and then re-opened the project. I tried the "rename" trick, above, and that didn't work, but perhaps the poster of that answer also closed the project - they didn't detail exactly what steps they went thru to rename it. (I found you don't have to close the project to rename it, but perhaps they did.)
< /rob>
In my case, I couldn't use an existing copy because I checked out the code using a newer version of Subversion on the command-line and Subclipse 1.4 couldn't recognize it. Upgrading and going through the improved "Share Project" menu resolved the problem.
I got this tip from the forums here:
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2380064
I had the same issue and here are the details of the fix.
My Eclipse is "Helios Service Release 1".
I had an SVN checkout on my filesystem, I went to New Java Project, unchecked Use default location, chose the location, went to next step, chose the source folder and said Finish.
The project came up with no disk icon on it. As per few forum posts, right-clicked on the project, went to Team > Share Project, chose SVN, clicked Next, and the option was only to share the files to the SVN Repository for the first time.
I said Cancel, and the option is to make changes to the SVN plug-in settings. Went to Window menu, chose Preferences, browsed Team> SVN. Chose the SVN Connector tab, changed the SVNKit 1.2.3 to SVNKit 1.3.5 and said OK.
Then, right clicked on the project, said Team> SVN, on the next screen, chose the option Use Project Settings and clicked Finish. The disk button came to the project and the SVN URL got displayed on it.
Add the repository to your list of repositories in subclipse by choosing Window->Show View->Other... and choose SVN->SVN Repositories. Put in all the necessary info to connect to the repository.
Next, right click the repository and choose "checkout". If the project doesn't already have an eclipse .project file, you can create a new project from the source. If it already has a .project file, it will import that .project and use that as your eclipse project locally.
It will definitively not work if you use a different version of svn to checkout, that the one that is supported by Eclipse. I had this problem as I used svn 1.6 to checkout but I had an older eclipse version that had only 1.5. Subclipse has its own build-in svn client (Actually, in two flavors if I am not mistaken).
Check that the subclipse version matches the svn client that you used to checkout. You can check the plugin version number for subclipse (Help -> About -> Click on subversion logo) and match it against svn --version
This worked for me:
1) Go to the 'SVN Repository Exploring' perspective and add a folder somewhere above your working copy
2) Close and open the Eclipse projects.
This should then be enough to get them recognized by Subclipse.
I have encountered a similar situation were existing projects would not get associated with the Subversive plugin. Unfortunately, none of the previous suggestions helped (renaming projects etc.). What has helped is removing projects from Eclipse by deleting them -- just the projects from Package Explorer and not the actual directories and files on disc (the deletion prompt has a special checkbox for that, which is unchecked by default) -- and reimporting the deleted projects as existing projects back.
Of course, as mentioned in some of the answers here, the relevant SVN repositories need to be registered with Eclipse before reimporting the projects. Otherwise, there would no repositories to re-associate the projects with.
When you open a versioned project (i.e., a project in SVN working copy) in Eclipse, that was never previously used with Subclipse, you need to perform these steps:
Right-click the project in Project Explorer.
Select Team | Share Project.
At this point Subclipse will tell you that "The project is already configured with SVN repository information". Click Next.
Subclipse automatically recognizes this project as versioned and all the features of the SVN plug-in should become available.