great, thanks, i'll give that a shot...
Emmanuel Venisse wrote: > > By default continuum 1.1 use a java cvs client where 1.0.3 used the native > cvs client. > It seems they don't work on the same way. > If you want to use the native cvs client, you can add the following > property in the startup script (wrapper.conf if you use the standalone > version or the webapp container startup script if you use the > webapp): > > -Dmaven.scm.provider.cvs.implementation=cvs_native > > Emmanuel > > jmartin a écrit : >> I have a Continuum project tied to a CVS repository with a build target >> that >> uses a shell script which is checked out from that repository. In >> Continuum >> 1.0.3, this script executes without error, however in 1.1-beta-3, the >> same >> script fails with a "Permission denied" error from /bin/sh. After >> looking >> in the working directory for this project, I found out that the >> executable >> permission is no longer set on the script used by the build target (or >> any >> of the other scripts in this project). This is not the case in the >> corresponding working directory for the Continuum 1.0.3 version of this >> project, nor is it the case when I check out the scripts manually from >> CVS >> on the command line (in both of those cases the scripts are, as expected, >> marked as executable). >> >> So does Continuum 1.1-beta-3 do anything to alter the permissions of the >> files that it checks out? If so, is there some way to keep that from >> happening? >> >> Any help would be much appreciated. Thanks... >> >> -john > > > -- View this message in context: http://www.nabble.com/Does-Continuum-1.1-beta-3-alter-permissions-on-checked-out-files--tf4673550.html#a13369472 Sent from the Continuum - Users mailing list archive at Nabble.com.
