I'm working on a project in Eclipse, and our version control is in Subversion. My exact Eclipse info is Eclipse CDT Mars, 4.5.1, with Subclipse 1.10.9 .
So, I created this extran file, and I want to add it to version control, but - for some reason that's grayed out on the team menu, along with some other items:
Why is that? Or rather, what could be the reasons for this?
The Add to Version Control option only shows up when the selected item has a Subversion status of "unversioned". I would guess that your file is already considered versioned or scheduled add by Subversion or maybe it is ignored.
Related
I have been using the Mercurial Eclipse for MCU projects in System Workbench for STM32 IDE for a while. It allowed me to right click on a file or folder and use the compare with option in the context menu to compare against other file versions from the Mercurial repository. Recently due to a lack of support for a newer MCU, I had to move to the STM32CubeIDE. It is still eclipse based so I expected that I could install Mercurial Eclipse and have the same functionality. But what I have found is that the compare with context menu does not give the option to compare against previous versions. Even in the history view, I cannot compare one changeset against another.
It does appear that STM32CubeIDE uses a newer Eclipse version. The Eclipse versions are:
For STM32CubeIDE
Version: 4.19.0.v20210303-1800
Build id: I20210303-1800
For System Workbench
Version: 4.6.3.v20170301-0400
Build id: M20170301-0400
Does anyone know if there is a way to get these context menus to work with the newer Eclipse version?
I have a project in my eclipse workspace. After eclipse is started and workspace checked popups a window "Project Upgrade" which says that one of mine projects is
... created with older release of Eclipse and/or related plugins.
And does propose me to upgrade my project.
I want to know what exactly does "project upgrade", which files it touches and what exact changes will provide to them. Is it documented somewhere? I didn't find any useful information in eclipse help.
I'm using eclipse helios. But I want to know if is it somewhere some place with change log of "project structure" through eclipse versions.
I have a project under version control (SVN), and I am using netbenas 7.3.1 as IDE. Fortunately netbeans recognized the version control from the start, and now uses different colors to show modified, new, etc files as following:
For the second project, I am using Eclipse 3.8 (basically, Eclipse IDE is integrated into the software, and I prefer to stick with that). This project is also under version control (git), but Eclipse does not recognize it. I found out that the version control settings in Eclipse is in Team | share Project, but still can not make it work!
How can I enable version control for my second project in Eclipse in a way that I also get the coloring feature (for modified, new files, etc).
You need EGit Team provider and it is included into Eclipse Kepler Standard package or you can install it from default eclipse update site from "Collaboration" category. Add git local repository clone into Git Repositories View and use "Import Projects..." from context menu to import projects from working area into workspace. After import projects are gonna be recognized as shared through git.
I am not sure about 3.8 but previous versions of Eclipse were not bundled with Git support. You need to install plugins like EGit to add Git support to Eclipse.
Everything should be straight-forward after you have that installed :) as you seems to know the right place (Team context menu) to work with version control system.
In my eclipse Indigo installation, I have the clearcase remote client (CCRC) perspective working - it's connecting the server just fine and the functionality is there. However, in the Java EE perspective most of the buttons are disabled.
When I edited a file in the Java EE perspective, it used to ask (with a previous version of CCRC and eclipse ganymede) if I wanted to check it out. However, now it merely asks if I want to make the file writable (default eclipse behaviour).
Basically most of the CCRC functionality in the Java EE perspective is disabled. I can see the buttons in the toolbar, but they are disabled (greyed out). Clearcase is also not showing up in the right-click context menu under Team.
Thoughts?
All recent CCRC (7.1.x) settings I managed are build on the same premiss:
That the .project and .classpath are part of the snapshot 'web' view which is a CCRC view.
That is what indicates eclipse that this eclipse project is managed under source control.
CCRC has considerably changed its way of running since 7.1 (2009 as this release notes history illustrates)
Since those eclipse definition files should be under source control anyway, this shouldn't be an inconvenient.
VonC - great comment. That was the issue - we're creating our projects outside the clearcase view and importing the code into that project. However, the correct way to make the buttons functional is to create the project within the folder where the view is. That will enable the checkin/checkout functionality.
Whether or not that is a bug in CCRC is left up to the reader - the way we used to do it with previous CCRC versions worked fine, but that is not the same way it's working now.
I downloaded Eclipse Indigo (3.7) M6, the 'classic' edition. I added subversive and egit.
Still, the team menu contains only 'apply patch'. No 'share'. Yes, I have restarted.
I can't find anything in the way of a setting that seems likely to have any effect.
1) you can restart with eclipse -clean to rebuild the extension registry cache (that should get updated when you add new plugins)
2) Check your Help>About>Installation details. Did the 2 SCMs install? Can you go to Window>Open Perspective>Other... and open the Git Repository Exploring perspective?
3) Check your error log ... has anything gone bad? http://wiki.eclipse.org/FAQ_Where_can_I_find_that_elusive_.log_file%3F
I have the same kind of problem (with subversion). My solution : Launch the old version of eclipse, use disconnect in the team menu, and relaunch the new version.