#574 Error opening any project: "Error checking out the project from remote repository"

[asiersar]

Steps:
- Open OmegaT
- Click on "Project -> Open"
- Select an already existing project, but not from Git or SVN. Any project.

An error window appears:
"Error checking out the project from remote repository: org.eclipse.jgit.api.error.InvalidRemoteException: Invalid remote: origin"

The project doesn't open.

OmegaT 2.6.3 from here:
http://sourceforge.net/projects/omegat/files/OmegaT%20-%20Latest/OmegaT%202.6.3/OmegaT_2.6.3_Beta_Linux.tar.bz2/download

System:
Fedora 18
Java version "1.7.0_17"
OpenJDK Runtime Environment (fedora-2.3.8.3.fc18-i386)
OpenJDK Client VM (build 23.7-b01, mixed mode, sharing)

[Didier Briel]

Your folder must contain a .git folder, which is why OmegaT is trying to download a team project.

It doesn't happen on normal projects.

Didier

[asiersar]

Yes, the problem was a .git folder, but it was not in the project's folder.

I cannot open a project if there is a .git folder in the project's folder or in any folder up in the folder hierarchy.

For instance, with this tree:

• asiersar/
• asiersar/translations1/
• asiersar/translations2/
• asiersar/translations1/openshot/
• asiersar/translations1/omegat/
• asiersar/translations1/.git
• asiersar/translations2/shotwell/

I cannot open the openshot and the omegat projects, but I can open the shotwell project.

Likewise, if I have this:

• asiersar/.git

I cannot open any of the three projects.

[Didier Briel]

Thank you for the detailed explanation.

Thinking about it, that's a normal behaviour of the Git/SVN libraries. The way Git and SVN (since 2.7) are working, there's a single .git/.svn folder at the root of the versionned working copy, so anything below that has to be considered as being part of the working copy.

As we're using standard libraries for that, we won't fix it, unfortunately.

Didier

[Ambrose Li]

But this makes OmegaT unusable if we ever want to use git, or incorporate OmegaT in a project that is already tracked by git. This is still an issue in 3.1.8.

[Didier Briel]

There are way around this:
See https://groups.yahoo.com/neo/groups/OmegaT/conversations/topics/33682

For instance, you can use --no-team

Didier

[Timothy Reaves]

This is very clearly a defect in OmegaT, and a fairly serious one at that. The fact that there is a work-around does not change that this is a defect.

Just because an OmegaT project is in a subfolder of a git repo doesn't mean that an app should be able to open it's own project! And that you blame the git/svn libraries is just bizarre. Yes, the project is in a git checkout, that is clear. That you fail to open it correctly is the developers of OmegaT's fault.