Zoe, As a Aries Commiter, you have the rights to commit something into SVN which is not the case for me. So I cannot commit using svn -->
Charles-Moulliards-MacBook-Pro:modules charlesmoulliard$ svn commit -m "Add text" Sending modules/jpaproject.mdtext svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/repos/asf/!svn/ver/1082937/aries/site/trunk/content/modules/jpaproject.mdtext' The procedure requiring a patch from CMS + open a ticket in Jira to commit the patch seems too complicated and in fact does not work (see ticket https://issues.apache.org/jira/browse/ARIES-597) So what solution do you suggest to simplify the procedure for persons who would like to improve Aries Documentation and (provide grants on aries-site for apache committers which are not Aries committer, ....) ? Regards, Charles On Fri, Mar 18, 2011 at 3:45 PM, zoe slattery <[email protected]> wrote: > On 18/03/2011 14:19, Charles Moulliard wrote: >> >> Here is a new patch that you can use to make a test >> > OK - not exactly sure what you wanted me to do with this but this is what I > did: > > Copied your file to patch.txt > Changed directory to where my site is checked out (aries/site) > cd content/modules > patch < patch.txt > used svn diff to check that it had been applied > svn commit -m "Apply CM patch" > > So, this was pretty straightforward. The checkin generates a staging build > of the site, your change is visible here: > > http://aries.staging.apache.org/modules/jpaproject.html > > So, I'm not sure what the issue was? > > Zoe > >> On Fri, Mar 18, 2011 at 3:14 PM, zoe slattery<[email protected]> >> wrote: >>>>> >>>>> Then the committer applying the patch >>>>> also needs the full site checked out and configured to build. >>>> >>>> This is not true. You should just be able to check out, apply patch, >>>> commit and use the CMS tooling to verify. >>> >>> Hmm - on second thoughts - strictly speaking you are right. >>> >>> Z >>> >>>>>> >>> > >
