Help Compiling Error : This Client Is Too Old To Work With Working Copy '.'

[HardCoreIV]

Here's the full error

 

version:
     [exec] Result: 1
     [echo] L2jFrozen Gameserver Revision: svn: This client is too old to work with working copy '.'.  You need
     [echo] to get a newer Subversion client, or to downgrade this working copy.
     [echo] See http://subversion.tigris.org/faq.html#working-copy-format-change
     [echo] for details

 

Despite that though... i still get : BUILD SUCCESSFUL

 

ps jdk 1.7

and this is what i installed to get the svn tabs : http://subclipse.tigris.org/update_1.10.x/

 

Thank you!

['Baggos']

Read this..

or press the button "Show"..

 

 

 

I got an error saying "This client is too old to work with working copy '...' ". How can I fix it without upgrading Subversion?

 

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn't work — it just gives the above error.

 

This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn't know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.

 

1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).

 

Subversion 1.7.0 and newer will not upgrade working copies unless you explicitly ask them to do so. (Upgrading the working copies is, however, required; Subversion 1.7.0 cannot operate on working copies created or used by earlier Subversions.)

 

Subversion 1.6.x and earlier automatically upgrade working copies when they first touch them. This behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:

http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py

Run that script with the "--help" option to see how to use it. (It can downgrade 1.6.x working copies to formats usable by Subversion 1.4.x and 1.5.x, but cannot downgrade 1.7.x working copies.)

 

As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

 

 

 

Also, Try to Install new software with this link:

http://subclipse.tigris.org/update_1.6.x/

Edited April 7, 2015 by 'Baggos'

[HardCoreIV]

 

Read this..

or press the button "Show"..

 

 

 

I got an error saying "This client is too old to work with working copy '...' ". How can I fix it without upgrading Subversion?

 

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn't work — it just gives the above error.

 

This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn't know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.

 

1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).

 

Subversion 1.7.0 and newer will not upgrade working copies unless you explicitly ask them to do so. (Upgrading the working copies is, however, required; Subversion 1.7.0 cannot operate on working copies created or used by earlier Subversions.)

 

Subversion 1.6.x and earlier automatically upgrade working copies when they first touch them. This behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:

http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py

Run that script with the "--help" option to see how to use it. (It can downgrade 1.6.x working copies to formats usable by Subversion 1.4.x and 1.5.x, but cannot downgrade 1.7.x working copies.)

 

As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

 

 

 

Also, Try to Install new software with this link:

http://subclipse.tigris.org/update_1.6.x/

 

Alright man! thanks! both builds were succesful! i knew it had something to do with this -> http://subclipse.tigris.org/update_1.10.x/i used this -> http://subclipse.tigris.org/update_1.6.x/ and it worked! fxaristw baggo ;)

 

you may lock this