enter image description here
There is any error. It works well. But intelliJ show me red text on files. How can I fix it.
Looks like VCS (git, subversion, etc) is configured in the project, but these files are excluded from it.
That's why they are marked red.
To add files to version control, choose the Add action in the Git submenu of the file context menu:
Related
We are working with building ETL packages in SSIS using a TFS repository. When my collegue add new files to the repository they are not added properly to the repository even though he checks in the entire project file. He sees the files in his project folder, and it looks like everything is checked in. But when I click on "Get latest version" I get a warning that the package is missing from the project directory. If any of us then try to add the file again we get a warning that the file all redy exists, even though it is not visible in my folders. Right now the solution we are using is for him to delete the file and then commit the change. After he deletes the file I get the latest version. Then he sends me the files and then I add them to the repository. Once I have added the files things seem to work as expected. Has anyone else had this problem, and know of a solution?
UPDATE:
The solution we found now is that I have to go to the local folder and find the new file my colegue added. Then I right click the file he just added and select add to project. Then the new file is visible in my version, but it does not have a blue lock icon next to it. If I then double click the sln-file to reload the project the blue lock icon is visible to me.
It is still not an optimal solution, but it works a lot better than him having to send me the file so I could check it in.
Is this the way TFS is supposed to work?
Can you please check the mapped work space path in your local machine there you will find the checked code. You need to manually Add.
Right Click on SSIS package -->AddExisting Package--> Select the package from Workspace-->Ok
Now you will find the missing package in your Solution Explorer as well.
If you are using TFVC.
Open Source Control Explorer=>Right click that solution/project folder=>View History, then check the related ChangeSet whether he add the file correctly.
Let your college to check the permission of that folder/file: Right click the folder/file->Advanced=>Security.
Regards
First I wasn't able to get anything on the Utilities tab on the far top left for the Identity Inspector, Size Inspector, etc.
When I tap on viewController I can't access anything. I can't navigate through the project either. Has this happened to anyone? I haven't changed the location of the project. However, I have synced the project to Github from my desktop. I'm using OS X El Capitan. This has happened for 2 projects... This is what it looks like:
This is what it looks like when I click the error:
Any help is appreciated.
Your project file has broken. Open up your project's root directory using SourceTree. You will see all the conflicting files.
Cntrl click on the project file and launch the external merge tool.
This should open FileMerge by default. You can scroll through the file to reveal the conflicts. The tool is a bit buggy and you might have to first scroll through all the text before the red markers are revealed in the right gutter.
On each of the red marked conflicts, select the highlighted section and choose the correct code. On the top of each section, it will say which repo is which, local vs remote.
At the bottom of the FileMerge app there is an option for resolving the selected conflict. Left, Right, Left then Right, etc. Once you have fixed all the conflicts, cmd + s to save it, then cmd + q to quit it. SourceTree should then show that the file is no longer conlficting.
If you then open Xcode you will get your file tree back, where you can then fix the remaining conflicts in Xcode or using the previous technique in SourceTree.
This situation should highlight another issue, you are doing something incorrectly with git. Maybe force pushing without pulling from the remote.
commit, pull, possibly fix conflicts, push.
I have a project hosted on GitHub, the active branch of which is called dev. Since yesterday, Aptana shows [dev+1] next to the project folder. Before yesterday, it's only shown [dev]. What does [dev+1] mean?
Please see the screenshot below:
Here is the answer from the Aptana Documentation: (I highlighted the important note)
Our Git support will make git-specific modifications to the UI for
related projects and files. In particular, unstaged files will
typically be shown with a red background color in Project and App
Explorer; staged will show with a green BG. Files with any uncommitted
changes will show with a * (asterisk) "dirty" indicator, and folders
will show the dirty indicator when any file inside it's hierarchy is
dirty. Projects will show the current branch inside square brackets to
the right of the project name inside the Project Explorer. The branch
name will be followed by a + or - and number if there are committed
changes to be pushed or pulled from a corresponding remote.
My project pane in IntelliJ has all files and folder in red color instead of the typical black. I can't find documentation on what does this color mean and how to fix whatever caused it so that it appears black again.
I notice that when I click on these files and folders, then choose Menu->VCS->Mercurial. It asks if I want to add them into source control. These files are already in Mercurial, perhaps this is a Mercurial problem?
Refer to help: File Status Highlights.
This can happen if there is an error with you VCS. To repair this:
Navigate to Settings | Version Control
Select the mapping(s)
Click [-] icon or press Delete to remove the mapping or change the association to None
Files added to xcode project show red on another Mac. Both the windows while adding files to the project look the same. When I re-add them in the newly opened project, it starts working fine. I need to know what's causing this.
When you add files to Xcode project, you would see "Copy items to destination group's folder". By default it's unchecked. So it copies references. When you move the resource that you added to Xcode to a different location on same computer or open in another computer it looks for that reference which is missing. So you see missing items as red.
If you check that box "Copy items to destination group's folder" when prompted for, you wouldn't see that.
There can be another reason. If you or someone have accidentally removed file from the Project folder from finder but not Xcode, you would see same effect.
There is an option in the project selecting if files should be stored with absolute or relative paths; it may be set to absolute. If it is, other machines will only be able to find the files if they are in the exact same location and not just in the same location relative to the project file.
You can test this by adding a file and saving the project then checking it in a text editor. Right click on the project in Finder and click "Show package contents." You can then open project.pbxproj (or something like that) in any text editor. You can even use Xcode. Find the file you just added and see how it is storing the path.
I managed to get everything red by accidentally moving the project folder.
After moving the directory back all files were red-marked.
I resolved this by clicking on the project root on the left pane
Clicking the arrow pointing right next to the "Full path" on the right pane under Identity.
By selecting another option and back the project refreshed itself.
I guess it depends on your preferred work environment but i continuously copy all my files over to avoid the dreaded red triangles.
xcode buggyness, you should try this next time:
rm -rf ~/Library/Developer/Xcode/DerivedData/