brazitech/p4nb

Automatically exported from code.google.com/p/p4nb

p4nb's Issues

Is this plugin still supported? Viable? getting 'Password (P4PASSWD' invalid or unset in NB8.0.2

What steps will reproduce the problem?
1.  Simple use in NB 8.0.2
2.
3.

What is the expected output? What do you see instead?

No error messages


What version of the product are you using? On what operating system?

1.4

Please provide any additional information below.

I notice that there has been no activity in this project since '09 - over 5 
years ago.  Is this still a Viable NB plugin?  Has it been canceled or moved to 
a different project?

This looks good except that I am getting errors with the password (which I know 
is correct):

From Output - Perforce:

[11:06:01.771] Perforce password (P4PASSWD) invalid or unset.

[11:06:03.160] Perforce password (P4PASSWD) invalid or unset.

[11:06:06.737] Perforce password (P4PASSWD) invalid or unset.

[11:06:08.032] Perforce password (P4PASSWD) invalid or unset.

[11:06:09.485] Perforce password (P4PASSWD) invalid or unset.

and on and on...

I can't add or edit files.

Original issue reported on code.google.com by [email protected] on 4 Mar 2015 at 7:07

Many temporary files created inside project

What steps will reproduce the problem?
1. just edit some file

What is the expected output? What do you see instead?
When I edit A.java I will get "/tmp/vcs-<timestamp>/A.java. These files
completely mess my project


What version of the product are you using? On what operating system?
org-heresylabs-netbeans-p4-alpha6.nbm + NB6.7 (and also 6.8m1), Linux

Running command like 
p4 -u *** -c *** -p * -P ******** print -o
"/tmp/vcs-1254530915674/ProjectNode.java" -q ProjectNode.java
means that quotes will be part of the file name. You may want to use 

sh -c 'p4 -u *** ... print -o "/tmp/cvs-XYZ/A.java" -q A.java

Or better yet use Runtime.exec(String[]) instead of Runtime.exec(String)
that is inherently prone to this kind of errors.

Original issue reported on code.google.com by [email protected] on 3 Oct 2009 at 1:01

Patch for http://code.google.com/p/p4nb/issues/detail?id=2

I do not see how to attach a file to an existing bug so here comes the patch.

Original issue reported on code.google.com by [email protected] on 3 Oct 2009 at 1:51

Attachments:

• p4nb.diff

There is no submit option in the plugin

What steps will reproduce the problem?
1. Add, edit or delete file
2. Try submitting files back to perforce

What is the expected output? What do you see instead?
There should be an option to submit files to perforce. Ideally you should
be able to submit the whole folder and uncheck unwanted files etc. Just
like visual studio plugin does and same way you can do in text file when
you do 'p4 submit' from the command line.

What version of the product are you using? On what operating system?
Version: 1.0 Source: org-heresylabs-netbeans-p4-alpha5.nbm

Original issue reported on code.google.com by stan.wozniak on 11 Jun 2009 at 4:36

p4 called with wrong working directory

Using netbeans 6.8 on Linux and the alpha7 of p4nb:

1. Configure connection with working directory, e.g. /home/wist/Perforce
and appropriate client workspace.
2. Open a project under the client-root, e.g. /home/wist/Perforce/ruby/tcb
3. Hit refresh

What is the expected output? What do you see instead?
Instead of the files getting updated with the attributes from Perforce, p4
is called again and again, because it fails with "Path <foo> is not under
client's root '/home/wist/Perforce'

Debugging p4nb in netbeans it seems as if everything should work fine:
In CliWrapper::procExecute(), Runtime.getRuntime().execute() get's called
with the correct p4 command and the parameter 'dir' is set to
/home/wist/Perforce/ruby/tcb'. However, somehow the underlying UNIXProcess
doesn't change the working directory.

Original issue reported on code.google.com by [email protected] on 4 Feb 2010 at 9:39

Losing label for "<default package>"

I have some projects with a hierarchy like this:
"Other Sources"
  "src/main/resources/"
    "<default package>"

After enabling this perforce plugin (thank you thank you thank you for
building this), the "<default package>" text turns blank.

I've never written a nb module, so I'm not sure why or if this is the right
way to fix this, but I can resolve it by replacing "<" and ">" with "&lt;"
and "&gt;" in the VCSAnnotator.

In particular, in PerforceVersioningSystem.java, in
annotatePerforceName(...), I add this to the top and bottom (where "name"
is returned).

replace:
return name;
with:
return name.replace("<", "&lt;").replace(">", "&gt;");

Original issue reported on code.google.com by [email protected] on 11 Nov 2009 at 2:57

Refactoring does not work for R/O files under SCM like Perforce

See original bug http://www.netbeans.org/issues/show_bug.cgi?id=173671

Product Version: NetBeans IDE 6.7 (Build 200906241340)
Java: 1.6.0_14; Java HotSpot(TM) 64-Bit Server VM 14.0-b16
System: Linux version 2.6.24-gg804003-generic running on amd64; UTF-8;
en_US (nb)
Userdir: /home/radimkubacki/.netbeans/6.7

I have a Perforce workspace - all files are typically checked out R/O. I
tried 'Change method signature' refactoring and
it silently failed to do anything and did not report failure either. 

I had to manually edit it first - this operation calls perforce plugin
correctly to do run 'p4 edit' to make the file
writable and after this the same refactoring passed. Obviously this
workaround is not very good solution for a
refactoring that touches more files.

According to discussion in the bug the interceptor's isMutable() should
return true for all files.

Original issue reported on code.google.com by [email protected] on 26 Oct 2009 at 8:19