maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (WAGON-287) Add Perforce support to Wagon SCM for deploy
Date Mon, 05 Oct 2009 23:05:28 GMT

     [ http://jira.codehaus.org/browse/WAGON-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated WAGON-287:
-------------------------------

    Fix Version/s: 1.0

> Add Perforce support to Wagon SCM for deploy
> --------------------------------------------
>
>                 Key: WAGON-287
>                 URL: http://jira.codehaus.org/browse/WAGON-287
>             Project: Maven Wagon
>          Issue Type: Bug
>          Components: wagon-scm
>    Affects Versions: 1.0-beta-6
>         Environment: Maven SCM 1.2 with SCM-496 and SCM-500 patched
>            Reporter: Andrey Ashikhmin
>             Fix For: 1.0
>
>         Attachments: p4-patch-against-wagon-scm-1.0-beta-6 .patch
>
>
> Currently Wagon SCM needs several things to allow perforce support (provided SCM-500
is fixed)
>  # Update dependencies to SCM version 1.2 or higher (check plexus-utils also)
>  # providerRepository.setPersistCheckout(true)
>  # As we don't edit or remove files from SCM in ScmWagon.putInternal, it doesn't make
sense to override checked out files (the override is in conflict with the read-only flag of
files synced from p4)
> I'm attaching a patch for issues #2 & #3 

-- 
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

        

Mime
View raw message