Thanks Andrew,
That made it.
I though hoped that by using
svn up -r1634839
It would also update the externals independently of the main repo revision
Like
svn up
alone does
Fair enough!
Jacques
Le 10/02/2015 12:44, Andrew Hemp a écrit :
> Hi Jacques,
>
> This should leave the externals properties as is:
>
> svn update -rXXX --ignore-externals
>
> cheers
>
> Andrew
>
> On 10 February 2015 at 13:36, Stefan Sperling <stsp_at_apache.org <mailto:stsp_at_apache.org>> wrote:
>
> On Tue, Feb 10, 2015 at 12:04:24PM +0100, jleroux_at_apache.org <mailto:jleroux_at_apache.org> wrote:
> > Hi,
> >
> > Today I tried to update a custom OFBiz working copy to a specific revision and got this
> >
> > C:\********>svn up -r1634839
> > Mise à jour de '.' :
> > U hot-deploy
> > Removed external 'hot-deploy\core'
> > Removed external 'hot-deploy\****po'
> > Left local modifications as 'hot-deploy\***po'
> > Removed external 'hot-deploy\********-theme'
> > Removed external 'hot-deploy\********hh'
> > Removed external 'hot-deploy\********comlead'
> > Removed external 'hot-deploy\********accnt'
> > Removed external 'hot-deploy\********common'
> > Left local modifications as 'hot-deploy\********common'
> > Removed external 'hot-deploy\productconfig'
> > Left local modifications as 'hot-deploy\productconfig'
> > Actualisé à la révision 1634839.
> >
> > C:\********>
>
> > Anybody an idea (did not find anything clear in Google)?
>
> Have the relevant svn:externals properties changed?
> If someone removed an external definition from the property (or removed the
> property entirely) then this behaviour would be entirely expected.
>
> If you need more help, please clearly state which URL you checked out and
> which revision numbers were involved so that others can reproduce your problem.
>
>
Received on 2015-02-10 14:13:01 CET