[ 
https://issues.apache.org/jira/browse/SCM-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960619#comment-17960619
 ] 

ASF GitHub Bot commented on SCM-179:
------------------------------------

jira-importer commented on issue #437:
URL: https://github.com/apache/maven-scm/issues/437#issuecomment-2964594469

   **[John Dennis 
Casey](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jdcasey)** 
commented
   
   fixed in SVN, and deployed a snapshot to the snapshot repository:
   
   http://cvs.apache.org/maven-snapshot-repository
   
   - added protected method on abstract scm mojo, to allow setting 
connectionType field.
   - added an overloaded parameter in the checkin mojo, to reset the 
default-value of the connectionType parameter...it's developerConnection for 
commits.
   
   




> scm:checkin uses <connection> not <developerConnection>
> -------------------------------------------------------
>
>                 Key: SCM-179
>                 URL: https://issues.apache.org/jira/browse/SCM-179
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-plugin
>            Reporter: Alex Mayorga Adame
>            Assignee: John Dennis Casey
>            Priority: Major
>             Fix For: 1.0-beta-3
>
>
> Looks like scm:checkin uses <connection> and not <developerConnection>. 
> http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_scm 
> states that <connection> is to be read-only.
> Below found case for a <connection> read-only that fails:
> {{...}}
> {{[DEBUG] Retrieving parent-POM: org.apache.maven.scm:maven-scm::1.0-beta-2 
> for project:}} {{null:maven-scm-providers:pom:1.0-beta-2 from the 
> repository.}}
> {{[DEBUG]   
> org.apache.maven.scm:maven-scm-provider-svn:jar:1.0-beta-2:runtime (selected 
> for runtime)}}
> {{[DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-scm-plugin:1.0-beta-2:checkin' -->}}
> {{[DEBUG]   (f) basedir = /export1/eae/am74839/esfSample}}
> {{[DEBUG]   (f) connectionUrl = 
> scm:cvs:pserver:[email protected]:/export1/cvsrep/eae:esfSample}}
> {{[DEBUG]   (f) message = -Fixed problems caused by change in CVS location}}
> {{[DEBUG]   (f) settings = org.apache.maven.settings.Settings@1f3ce5c}}
> {{[DEBUG] -- end configuration --}}
> {{[INFO] [scm:checkin]}}
> {{[DEBUG] cvsRoot: 
> :pserver:[email protected]:2401/export1/cvsrep/eae}}
> {{[DEBUG] passFile: /home/am74839/.cvspass}}
> {{[DEBUG] cvsroot 
> :pserver:[email protected]:2401/export1/cvsrep/eae already exist 
> in}}
> {{/home/am74839/.cvspass. SKIPPED.}}
> {{[DEBUG] Working directory: /export1/eae/am74839/esfSample}}
> {{[DEBUG] Command line: cvs -f -d 
> :pserver:[email protected]:/export1/cvsrep/eae -q commit -R -F}} 
> {{/var/tmp/scm-commit-message55027.txt}}
> {{[ERROR] Provider message:}}
> {{[ERROR] The cvs command failed.}}
> {{[ERROR] Command output:}}
> {{[ERROR] cvs [server aborted]: "commit" requires write access to the 
> repository}}
> {{...}}
> Relevant part of POM:
> {{...}}
> {{<scm>}}
> {{<connection>scm:cvs:pserver:[email protected]:/export1/cvsrep/eae:esfSample</connection>}}
> {{<developerConnection>scm:cvs:pserver:${user.name}@gcatfs1d.ny.ssmb.com:/export1/cvsrep/eae:esfSample</developerConnection>}}
> {{</scm>}}
> {{...}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to