You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "gary fry (JIRA)" <ji...@codehaus.org> on 2011/01/27 16:34:03 UTC
[jira] Created: (MRELEASE-639) Anthill Pro build server expects to
be logged into Perforce. Using the release plugin, a perforce login is
invoked continuously.
Anthill Pro build server expects to be logged into Perforce. Using the release plugin, a perforce login is invoked continuously.
---------------------------------------------------------------------------------------------------------------------------------
Key: MRELEASE-639
URL: http://jira.codehaus.org/browse/MRELEASE-639
Project: Maven 2.x Release Plugin
Issue Type: New Feature
Affects Versions: 2.1
Environment: Anthill Pro/Perforce, maven-scm-provider-perforce
Reporter: gary fry
Attachments: PerforceLoginCommand.java, PerforceLoginCommandTest.java
Currently we have a build system that relies on a Perforce client to be continuously logged in. We have taken a fork of the release plugin to make it work this way. ie we've commented out the login code. A better solution is to make this available for others with similar problems.
If a property was provided, it would enable bypassing the Perforce login command. Attached suggested fix.
if -Dmaven.scm.perforce.perform.login is not coded, default behaviour occurs (ie p4 login)
if -Dmaven.scm.perforce.perform.login=true is coded, default behaviour occurs (ie p4 login)
if -Dmaven.scm.perforce.perform.login=false is coded, no Perforce login occurs and a warning is logged.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-639) Anthill Pro build server expects to
be logged into Perforce. Using the release plugin, a perforce login is
invoked continuously.
Posted by "gary fry (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gary fry closed MRELEASE-639.
-----------------------------
Resolution: Not A Bug
Used the existing "feature" of not specifying a P4PASSWD to work-around. This issue is no longer relevant.
> Anthill Pro build server expects to be logged into Perforce. Using the release plugin, a perforce login is invoked continuously.
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-639
> URL: http://jira.codehaus.org/browse/MRELEASE-639
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Affects Versions: 2.1
> Environment: Anthill Pro/Perforce, maven-scm-provider-perforce
> Reporter: gary fry
> Attachments: PerforceLoginCommand.java, PerforceLoginCommandTest.java
>
>
> Currently we have a build system that relies on a Perforce client to be continuously logged in. We have taken a fork of the release plugin to make it work this way. ie we've commented out the login code. A better solution is to make this available for others with similar problems.
> If a property was provided, it would enable bypassing the Perforce login command. Attached suggested fix.
> if -Dmaven.scm.perforce.perform.login is not coded, default behaviour occurs (ie p4 login)
> if -Dmaven.scm.perforce.perform.login=true is coded, default behaviour occurs (ie p4 login)
> if -Dmaven.scm.perforce.perform.login=false is coded, no Perforce login occurs and a warning is logged.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira