After a bit of research, I think that this is a limitation of the
current svn diff format.
See for example the comments under this post:
http://ariejan.net/2007/07/03/how-to-create-and-apply-a-patch-with-subversion/We may do the following to facilitate the migration and contribution
from the community.
1) a committer with global access to the OFBiz svn repository runs a
script that simply renames (svn rename) all the bsh files to groovy
files; then another script to update the include directives for the
scripts (in widget definitions and, for a few of them, in the
controller)
2) everything is committed
3) then the new groovy files (that should work as the original bsh
files) can be enhanced and further migrated by the contributors
following the standard approach of Jira/patch files
Jacopo
On May 30, 2008, at 3:06 PM, Ashish Vijaywargiya wrote:
> Hello,
>
> I was trying to work on a Groovy conversion from the Beanshell file.
> For this I tried "svn rename" command from the Terminal.
>
> But when I had put the "svn diff" command then it is showing me the
> contents
> of old file that is renamed to new file.
> So how can I get the contents of the new file i.e *.groovy in the
> patch file
> with the history information maintained in it ?
>
> In general I don't use the trunk for the development that I use for
> commiting the code.
> Usually I test all the code in some other instance of trunk and then
> put the
> patch on the trunk that I use for commiting the code.
>
> Early help from anybody will be appreciated.
> Thanks !!!
>
> --
> Ashish Vijaywargiya
Locked
