headers
hitesh1903 | 4 Jan 2012 00:15
Favicon

[p4] p4scc and symlinks


Posted on behalf of forum user 'hitesh1903'.

Hello All,

Version 2011.1 now supports symbolic links on windows. Hurray!!!

The excitement lasted only a few hours until I realized that even the newest
version of p4scc still doesn't resolve symbolic links.

Example:
File => C:\Folder1\File1.txt
Symbolic link => C:\SymLink1 with target being C:\Folder1

When the file C:\SymLink1\File1.txt is opened in Visual Studio, p4scc
cannot resolve the path to check out the appropriate/true file.

Is there a work around to this??

Cheers,
Hitesh

--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/1347-p4scc-and-symlinks
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
(Continue reading)

Permalink | Reply | 8 comments |
headers
Matt Janulewicz | 4 Jan 2012 00:45
Favicon

Re: [p4] p4scc and symlinks

I believe you can add the physical file (C:\Folder1\File1.txt) as a Solution Item and the link will 'line
up', coincidentally.

-Matt

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-
> bounces <at> perforce.com] On Behalf Of hitesh1903
> Sent: Tuesday, January 03, 2012 3:15 PM
> To: perforce-user <at> perforce.com
> Subject: [p4] p4scc and symlinks
>
>
> Posted on behalf of forum user 'hitesh1903'.
>
> Hello All,
>
> Version 2011.1 now supports symbolic links on windows. Hurray!!!
>
> The excitement lasted only a few hours until I realized that even the
> newest
> version of p4scc still doesn't resolve symbolic links.
>
> Example:
> File => C:\Folder1\File1.txt
> Symbolic link => C:\SymLink1 with target being C:\Folder1
>
> When the file C:\SymLink1\File1.txt is opened in Visual Studio, p4scc
> cannot resolve the path to check out the appropriate/true file.
>
(Continue reading)

Permalink | Reply | 7 comments |
headers
Ross Olson | 4 Jan 2012 01:25
Favicon

Re: [p4] Great Design


Posted on behalf of forum user 'Ross Olson'.

This actually seems to be a common issue across a lot of tools I've seen
lately. Developers seem to be working on big and bigger monitors, never noticing
that they're taking up the whole 24" screen and causing problems for
people working on laptops. I've seen similar problems in the Chronicle
interface.

--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/1345-great-design
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 1 comment |
headers
Heinz, Ines | 4 Jan 2012 01:52

Re: [p4] Great Design

I have a huge monitor which I use to run multiple tools.  It bothers me when one tool hogs a disproportionate
amount of the screen.  The assumption by any given tool that their interface is the only necessary
interface is short-sighted.  Users will run multiple applications and want different interfaces for
each of them.  If a tool makes this difficult, this will cause users to migrate to different tools.  After
all, we might want to play solitaire, check our email, and develop code at the same time!

Ines
======================================
Aura Ines Heinz, WCI LC Liaison
Lawrence Livermore National Laboratory
L-98 7000 East Ave Livermore CA 94551
heinz2 <at> llnl.gov
925-423-7900(work) 
925-423-5209(fax)
925-579-4415(mobile)
======================================

-----Original Message-----
From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-bounces <at> perforce.com] On Behalf
Of Ross Olson
Sent: Tuesday, January 03, 2012 4:25 PM
To: perforce-user <at> perforce.com
Subject: Re: [p4] Great Design

Posted on behalf of forum user 'Ross Olson'.

This actually seems to be a common issue across a lot of tools I've seen
lately. Developers seem to be working on big and bigger monitors, never noticing
that they're taking up the whole 24" screen and causing problems for
people working on laptops. I've seen similar problems in the Chronicle
(Continue reading)

Permalink | Reply | 0 comments |
headers
Timo Naroska | 4 Jan 2012 15:50
Favicon

[p4] p4maven and OTP authentication


Posted on behalf of forum user 'Timo Naroska'.

I want to use the p4maven scm plugin in a mvn build.

The perforce servers in our environment are configured to require
One-Time-Password authentication. So, I cannot configure a static scm password
in pom.xml.
Without password I get the NPE below.

Is there way to configure p4maven to not try to login itself, but rely on an
existing p4 ticket as is done by the maven-scm-provider-perforce (  
http://maven.apache.org/scm/maven-scm-providers/maven-scm-provider-perforce/ )?

com.perforce.p4java.exception.ConnectionException: No login password passed to
client login at
com.perforce.p4java.impl.mapbased.rpc.packet.RpcPacketDispatcher.dispatch(RpcPacketDispatcher.java:220)
at
com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmd(OneShotServerImpl.java:270)
at
com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmd(OneShotServerImpl.java:193)
at
com.perforce.p4java.impl.mapbased.rpc.OneShotServerImpl.execMapCmd(OneShotServerImpl.java:176)
at com.perforce.p4java.impl.mapbased.server.Server.execMapCmd(Server.java:3981)
at com.perforce.p4java.impl.mapbased.server.Server.login(Server.java:593) at
com.perforce.maven.scm.provider.p4.command.P4ServerExecutor.initServer(P4ServerExecutor.java:115)
at
com.perforce.maven.scm.provider.p4.command.P4ClientExecutor.initP4(P4ClientExecutor.java:159)
at
com.perforce.maven.scm.provider.p4.command.P4Executor.<init>(P4Executor.java:432)
(Continue reading)

Permalink | Reply | 0 comments |
headers
P4Chris | 4 Jan 2012 17:20
Favicon

Re: [p4] P4V Switching Workspaces, Windows Explorer Plugin, and Environment Settings


Posted on behalf of forum user 'P4Chris'.

[http://forums.perforce.com/index.php?app=forums&module=forums&section=findpost&pid=4179]
Louis, on 2011/12/20 22:10:48 UTC, said:
>    I have clarified that P4V is updating some registry values (P4CLIENT, P4EDITOR, P4PORT, and P4USER) and
the Windows Explorer Plugin is using these values, but still it does not update these values quickly. Is it
possible to improve the timing by which these values are updated?
>   
>   Louis
>   

Hi Louis, 

Once installed, the behavior of P4V is not to change the environment variables,
though they can be changed (or more or less over-ridden) from within P4V or
changed with the 'p4 set' command from the command line client. In this
case it appears you are seeing P4V changing and storing environment variables in
the registry? I'm not saying this behavior doesn't occur, it does, but
it might be intended. Some extra context, aside from switching or using multiple
workspaces, would be helpful. 

What might be more appropriate, is to put together a case that you have, and
what you would like to see and/or what you are not seeing that you think you
should be seeing, and contact us in support. support <at> perforce.com. We can better
bring support resources to determine if this is a bug, enhancement request, or
possibly even intended behavior.

--
Please click here to see the post in its original format:
(Continue reading)

Permalink | Reply | 1 comment |
headers
jfritz42 | 4 Jan 2012 19:00
Favicon

[p4] Cannot import a project in Eclipse


Posted on behalf of forum user 'jfritz42'.

I'm running Eclipse on a Linux platform using the Perforce plugin.

I'm going to File->New->Project...->Perforce->Projects from
Perforce, choose my Perforce connection, then select the project directory from
the depot. I'm then getting the following error dialog:

Project import failed:
------------
The following project(s) could not be imported because they are not mapped in
the Perforce client view:
//depot/Android/Mainline/Utility/XAPI

This really confusing, because the client view looks fine. I am mapping both the
entire depot as well as the specific project folder.
//depot/... //workspace/...
//depot/Android/Mainline/Utility/XAPI/...
//workspace/Android/Mainline/Utility/XAPI/...

Any ideas? I've tried searching on Google but can't find any solutions.
I'm using Eclipse Indigo Service Release 1. The Perforce plug-ins are
version 2010.1.275861. All software is up to date.

--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/1349-cannot-import-a-project-in-eclipse
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
(Continue reading)

Permalink | Reply | 1 comment |
headers
hitesh1903 | 4 Jan 2012 20:45
Favicon

Re: [p4] p4scc and symlinks


Posted on behalf of forum user 'hitesh1903'.

Your solution would completely beat the purpose of having symbolic links.
Moreover, it doesn't solve the problem at all since if I have the
C:\SymLink1\File1.txt open in Visual Studio it would try to check that
file out instead of the actual file.

The only solution I can imagine requires p4scc actually resolving symbolic paths
which isn't happening at the moment.

--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/1347-p4scc-and-symlinks
_______________________________________________
perforce-user mailing list  -  perforce-user <at> perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
Permalink | Reply | 6 comments |
headers
Matt Janulewicz | 4 Jan 2012 21:24
Favicon

Re: [p4] p4scc and symlinks

I believe this is just how symbolic links work. They're symbolic, not actual. If you check out a symlink in p4
using commandline, P4V, whatever, it checks out the actual <link>, not the file it points to. The link is a
filesystem object. It's not smart. Never has been in p4.

Putting the actual file in Solution Items will at least sync that file and show them properly within the
solution, unless I'm misunderstanding what you mean by 'open' in your original post. Do you mean that
VisualStudio won't even allow you to view the file when the link is clicked in VisualStudio?

In any case, from what I'm reading, this is expected and understood behavior for symlinks.

-Matt

> -----Original Message-----
> From: perforce-user-bounces <at> perforce.com [mailto:perforce-user-
> bounces <at> perforce.com] On Behalf Of hitesh1903
> Sent: Wednesday, January 04, 2012 11:45 AM
> To: perforce-user <at> perforce.com
> Subject: Re: [p4] p4scc and symlinks
>
>
> Posted on behalf of forum user 'hitesh1903'.
>
> Your solution would completely beat the purpose of having symbolic
> links.
> Moreover, it doesn't solve the problem at all since if I have the
> C:\SymLink1\File1.txt open in Visual Studio it would try to check that
> file out instead of the actual file.
>
> The only solution I can imagine requires p4scc actually resolving
> symbolic paths
(Continue reading)

Permalink | Reply | 5 comments |
headers
Thandesh V.K | 5 Jan 2012 07:41
Picon

Re: [p4] clearcase to perforce [ How to handle the old workflow ]

Personal branch with all files branched is a bad choice.
Sparse Branching is the way to go for this -
http://kb.perforce.com/article/890/sparse-branching

You can make it easy for developers by wrapping sparse branching inside
some scripts so they don't have to deal with it.

On Thu, Jan 5, 2012 at 11:50 AM, Biswajit Dash <biswajitind <at> yahoo.com>wrote:

> Hi All,
> I am looking for suggestion to handle the workflow used with clearcase (or
> an alternate one)
> after a migration from clearcase to perforce.
>
> With clearcase,
>  Every developer use to create a private branch for each fix ( or a set of
> fixes, sometimes )
> A set of folks then take these branches 5-10 at a time and integrate/merge
> them into a newly created branch.
> perforce build/test on that branch, and everything is fine, merge the
> changes upward (promote to next level)
>
> What should be done when the codebase is move from clearcase to perforce.
>
> - I had encountered one organization where similar technique was used in
> perforce and old personal branches (more than a year old) were obliterated.
> - Another alternative I can think of is, having team branches. Different
> teams will have common branch. and after build/test we can either promote
> the team branch as a entirely or perform selective integration, in case
> some fix is not good and needs to be left out.
(Continue reading)

Permalink | Reply | 2 comments |

Gmane