|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
I think part of the reason 2 was implemented like that is that perforce doesn't really have a tool home in the same sense that tools like ant or java have homes. When you download the perforce client, you literally just get a single executable binary. With tools like this one (git, etc) providing the full path to the executable makes more sense.