History
|
Log In
H
OME
B
ROWSE PROJECT
F
IND ISSUES
Q
UICK SEARCH:
Learn more about
Quick Search
Issue Details
(
XML
|
Word
|
Printable
)
Key:
SCM-186
Type:
Bug
Status:
Closed
Resolution:
Fixed
Priority:
Critical
Assignee:
Mike Perham
Reporter:
John Didion
Votes:
0
Watchers:
0
Operations
If you were
logged in
you would be able to see more operations.
Maven SCM
Using the wrong command-line option to set the perforce host
Created:
18/Apr/06 03:06 PM
Updated:
13/Aug/06 08:01 PM
Component/s:
maven-scm-provider-perforce
Affects Version/s:
None
Fix Version/s:
1.0-beta-4
Time Tracking:
Not Specified
Complexity:
Intermediate
Description
« Hide
In PerforceScmProvider.createP4Command, you are using -H to set the perforce host. The option should actually be -p. -H sets the hostname of the client. Horrible terminology, I agree.
See for info:
http://www.perforce.com/perforce/doc.052/manuals/cmdref/env.P4PORT.html#1040647
Description
In PerforceScmProvider.createP4Command, you are using -H to set the perforce host. The option should actually be -p. -H sets the hostname of the client. Horrible terminology, I agree. See for info:
http://www.perforce.com/perforce/doc.052/manuals/cmdref/env.P4PORT.html#1040647
Show »
All
Comments
Work Log
Change History
Sort Order:
[
Permlink
|
« Hide
]
John Didion
-
18/Apr/06 03:16 PM
I marked this critical because it breaks the tag command. It may break others as well.
[
Show »
]
John Didion
-
18/Apr/06 03:16 PM
I marked this critical because it breaks the tag command. It may break others as well.