maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Tran (JIRA)" <j...@codehaus.org>
Subject [jira] (SCM-760) remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement
Date Mon, 23 Jun 2014 16:56:10 GMT

     [ https://jira.codehaus.org/browse/SCM-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dan Tran updated SCM-760:
-------------------------

    Description: 
Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its
path, however, it also expects special settings  from environment as well at at the remote
server.   This make it very tough to set up and run out the box.

It is better to defer this back to the provider itself and run plugin integration test



  was:
Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on its
path, however, it also expects special settings  from environment as well at at the remote
server.   This make it very tough to set up and run out the box.

It is better to defer this back to the provider itself and run plugin integration test

Also this should not work since the url 

{code }
     scm:perforce:///${basedir}/target/repository/trunk    is invalid at least at windows
( c:/ is not a valid remote path )
{code}


> remove maven-scm-plugin's RemoveMojoTest due to specific Perforce setup requirement
> -----------------------------------------------------------------------------------
>
>                 Key: SCM-760
>                 URL: https://jira.codehaus.org/browse/SCM-760
>             Project: Maven SCM
>          Issue Type: Task
>          Components: maven-plugin
>    Affects Versions: 1.9
>            Reporter: Dan Tran
>            Assignee: Dan Tran
>             Fix For: 1.10
>
>
> Currently this test uses P4 for its scm repo, and only runs when p4(.exe) detected on
its path, however, it also expects special settings  from environment as well at at the remote
server.   This make it very tough to set up and run out the box.
> It is better to defer this back to the provider itself and run plugin integration test



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message