[#IDEA-13127] Perforce regression: Path X is not under client's root Y

IDEA: Feedback

Perforce regression: Path X is not under client's root Y

Created: 06 Jun 07 20:43 Updated: 01 Nov 07 21:20

Component/s:

Version Control Integration. Perforce

Environment:

« Hide

Mac OS 10.4.9
JDK 5 & 6 DP are installed

Perforce version: Rev. P4/MACOSX104PPC/2006.2/112639 (2006/12/14).
Perforce server version: P4D/LINUX26X86/2007.2/122958 (2007/05/23)

Build:	7,002
Severity:	High

Description

« Hide

Perforce integration has not completely worked for me in Selena builds since 6951 (both 6981 and 7002 exhibits problems). There are various places where I see problems, but the easiest is selected "Update Project..." from the Version Control menu. When doing so I see the following error message: "Error:Path '/Users/reden/Documents/NEXVU/projects/mainline/...' is not under client's root '/Users/reden/Documents/NEXVU/working/'."

"/Users/reden/Documents/NEXVU/projects/mainline/" is my project location and is indeed not under my version control root location. I have no idea why it's trying to sync something in that location.

Here's my configuration information:

Platform: Mac
IDEA is using JDK 5 (note: I do have JDK 6 installed, but I edit IDEA's config to make sure it runs under 5)

Perforce is not using P4CONFIG.
Port: perforce.nexvu.com:1666
User: reden
Client: reden_galaxy
Password: <set to a non-empty password>
Use login authentication: no
Use native Perforce API: no
Path to executable: /Users/reden/bin/p4

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Dmitry Jemerov - 06 Jun 07 20:45

If your .ipr file is outside of the versioned root, you should set Version Control to <none> for the directory containing the .ipr file in Directory Version Control Configuration.

Does that fix the problem for you?

[ Permlink | « Hide ]

Robert Eden - 06 Jun 07 23:01

Hi Dmitry -

Yes, that did fix the issue.

It still seems like a bug (or possible an enhancement request) to me for three reasons:
1) It used to work. Behavior changed with the last two EAP releases.
2) That's really obscure. I never would have thought to do that.
3) It's clear from the Perforce client spec that it's not under my depot root. It should be easy to programmatically figure that out and exclude anything outside the versioned root.

Thanks for the help, though. I can use the latest EAP's now, which is great.

Rob

[ Permlink | « Hide ]

James Cooper - 09 Aug 07 20:30

I also found this to be a problem, although the steps Dmitry suggested work.

I would have thought a strategy to fix this is to only try and obtain VCS information about directories which are configured as "content roots" in the project/module configuration, irrespective of where the project files live?

[ Permlink | « Hide ]

Dmitry Jemerov - 09 Aug 07 20:50

We intentionally changed this behavior since version 6.0, in order to enable versioning of project files regardless of whether they live under module content roots. So your suggested fix strategy would be simply a revertion to the old behavior.

[ Permlink | « Hide ]

Robert Eden - 09 Aug 07 21:05

It's pretty un-intuitive, so I guess I'd vote for reverting to the old behavior. Another way of doing it could be to default to excluding everything not under the project path. Then, you could add an option to disable the default (i.e., enable versioning of files not under the project root) which would allow the current behavior.

[ Permlink | « Hide ]

Weston H Clark - 01 Nov 07 20:57

I'm getting that message, but a different set of steps. Running on 7.0.1, I normally work in one project, but I opening another project yesterday. When I switched back to my normal project, and I try to check out a file, I get the error above, but the it says my client root is the root of the project I was working on before, despite the face I have explicitly opened the .ipr file for the usual project.

[ Permlink | « Hide ]

Weston H Clark - 01 Nov 07 21:20

I remember my machine crashed with a BSOD over night, so my IJ system files may be corrupt. I have deleted them and restarted IJ. Didn't help. IJ just froze. I'm going to uninstall IJ and start all over. Sorry to put noise into this Jira.