[jira] Closed: (MRELEASE-639) Anthill Pro build server expects to be logged into Perforce. Using the release plugin, a perforce login is invoked continuously.
[ 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
[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] Created: (MRELEASE-650) Perforce Client Where command prefixes a hyphen when returning source location on *nix
Perforce Client Where command prefixes a hyphen when returning source location on *nix -- Key: MRELEASE-650 URL: http://jira.codehaus.org/browse/MRELEASE-650 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.2 Environment: Linux, Perforce client, Anthill Pro Reporter: gary fry Attachments: PerforceWhereCommand.java, PerforceWhereCommandTest.java Performing the following command on a *nix box: mvn -X --batch-mode -DupdateBranchVersions=true -DuseArtifactIdforBranchTag=true -DbranchName=GARY release:clean release:branch Returns: DEBUG] Executing: /bin/sh -c p4 where /[censored]/Branch/pom.xml [DEBUG] -//depot/se/multi-module-test/pom.xml //com.xxx.multi.module_parent_HEAD_Branch-3936/pom.xml /[censored]/Branch/pom.xml [DEBUG] Actual POM location: -//depot/se/multi-module-test [INFO] The SCM location in your pom.xml (//depot/se/multi-module-test) is not equal to the depot location (-//depot/se/multi-module-test). This happens frequently with branches. Ignoring the SCM location. [DEBUG] Sending changelist: Change: new Description: [maven-release-plugin] prepare branch GARY Files: -//depot/se/multi-module-test/pom.xml -//depot/se/multi-module-test/versionless-module/pom.xml -//depot/se/multi-module-test/versioned-module/pom.xml [ERROR] CommandLineException Exit code: 1 - Error in change specification. Can't include file(s) not already opened. Open new files with p4 add, p4 edit, etc. Command line was:p4 -d /[censored]/Branch submit -i org.codehaus.plexus.util.cli.CommandLineException: Exit code: 1 - Error in change specification. Can't include file(s) not already opened. Open new files with p4 add, p4 edit, etc. Command line was:p4 -d /[censored]/Branch submit -i at org.apache.maven.scm.provider.perforce.command.checkin.PerforceCheckInCommand.executeCheckInCommand(PerforceCheckInCommand.java:88) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:53) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.perforce.PerforceScmProvider.checkin(PerforceScmProvider.java:186) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:356) at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:159) at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:148) at org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:75) at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:79) at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:389) at org.apache.maven.shared.release.DefaultReleaseManager.branch(DefaultReleaseManager.java:360) at org.apache.maven.plugins.release.BranchReleaseMojo.execute(BranchReleaseMojo.java:235) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Attached a fix, based on 1.4 version of the maven-scm-provider-perforce artifact -- This message is automatically generated by JIRA. - If you think it was sent incorrectly con
[jira] Commented: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206613#action_206613
]
gary fry commented on MNG-3328:
---
Would be great if you could marry OS and Properties as an AND condition.
For example,
unix
my-prop-2
another-value
Currently, Maven2 looks for the first condition that is true, and the profile
is activated. However, this is not very useful if the build needs to run in
both Windows and Unix environments and you need to do something slightly
different on each OS, where activation is also determined by a property being
set at buld time
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 3.x
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
> {code:xml}
>
>
> some-value
> another-value
>
>
> {code}
> This would provide more flexibility in profile activation.
--
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] Issue Comment Edited: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206613#action_206613
]
gary fry edited comment on MNG-3328 at 1/12/10 10:34 AM:
-
Would be great if you could marry OS and Properties as an AND condition.
For example,
{code:xml}
unix
my-prop-2
another-value
{code}
Currently, Maven2 looks for the first condition that is true, and the profile
is activated. However, this is not very useful if the build needs to run in
both Windows and Unix environments and you need to do something slightly
different on each OS, where activation is also determined by a property being
set at buld time
was (Author: gary.fry):
Would be great if you could marry OS and Properties as an AND condition.
For example,
unix
my-prop-2
another-value
Currently, Maven2 looks for the first condition that is true, and the profile
is activated. However, this is not very useful if the build needs to run in
both Windows and Unix environments and you need to do something slightly
different on each OS, where activation is also determined by a property being
set at buld time
> Allow multiple profile activation properties.
> -
>
> Key: MNG-3328
> URL: http://jira.codehaus.org/browse/MNG-3328
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Profiles
>Affects Versions: 2.0.8
>Reporter: Paul Gier
> Fix For: 3.x
>
>
> The pom model should be changed to allow multiple properties to activate a
> profile. So the profile activation section could look something like this:
> {code:xml}
>
>
> some-value
> another-value
>
>
> {code}
> This would provide more flexibility in profile activation.
--
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
