featured project, update of SVN URLs

Two bits of news related to SourceForge:

  1. We’re going to be one of SF’s featured projects for the week of 8 April, which means that a link to VASSAL will appear on SF’s front page. This might mean we have a few more downloads and new visitors to the forum than usual in the coming week. (It would be best if we could get 3.2.4 released before then, as well.)

  2. SF is rejiggering their project setups. I’ve been getting emails about this for a few months now urging me to flip the switch to the new project setup, but wanted to avoid doing it until we had to. We’re to that point now. The only respect in which I know this will affect us is that our SVN URLs wll change to… something different from how they are now… but I don’t know exactly what they’ll be yet. The command for switching a working copy to the new URL will be “svn relocate NEWURL”, and I’ll post it here when I know what NEWURL is.

Thus spake uckelman:

  1. SF is rejiggering their project setups. I’ve been getting emails
    about this for a few months now urging me to flip the switch to the new
    project setup, but wanted to avoid doing it until we had to. We’re to
    that point now. The only respect in which I know this will affect us is
    that our SVN URLs wll change to… something different from how they are
    now… but I don’t know exactly what they’ll be yet. The command for
    switching a working copy to the new URL will be “svn relocate NEWURL”,
    and I’ll post it here when I know what NEWURL is.

The old base URL for our SVN repository was:

https://vassalengine.svn.sourceforge.net/svnroot/vassalengine/

The new base URL for our SVN repository is via svn+ssh is:

svn+ssh://YOURSFUSERNAME@svn.code.sf.net/p/vassalengine/svn/

The new base URL via https is:

https://svn.code.sf.net/p/vassalengine/svn/

If you have some part of our SVN repo checked out, “svn info” will
tell you a bunch of stuff. This is what I see for my working copy of
the trunk:

[uckelman@scylla trunk]$ svn info
Path: .
Working Copy Root Path: /home/uckelman/workspace/trunk
URL: https://vassalengine.svn.sourceforge.net/svnroot/vassalengine/VASSAL-src/trunk
Repository Root: https://vassalengine.svn.sourceforge.net/svnroot/vassalengine
Repository UUID: 67b53d14-2c14-4ace-a08f-0dab2b34000c
Revision: 8628
Node Kind: directory
Schedule: normal
Last Changed Author: uckelman
Last Changed Rev: 8628
Last Changed Date: 2013-04-04 13:37:55 +0200 (Thu, 04 Apr 2013)

The URL I need to update is the one on the line labeled “URL:”. To do
that, I replace the old base URL with the new one, leaving the last bit,
“VASSAL-src/trunk”, unchanged:

svn relocate svn+ssh://uckelman@svn.code.sf.net/p/vassalengine/svn/VASSAL-src/trunk

That was all I had to do to update my working copy of the trunk.


J.

Eclipse Users

As I have painfully discovered this morning, unless you are running the latest (4.2 Juno) version of Eclipse, you will not be able to access the new Sourceforge repository. Sourceforge uses version 1.7 of SVN which is only available in Juno.

Thus spake Brent Easton:

Eclipse Users

As I have painfully discovered this morning, unless you are running the
latest (4.2 Juno) version of Eclipse, you will not be able to access the
new Sourceforge repository. Sourceforge uses version 1.7 of SVN which is
only available in Juno.

That’s annoying. Sorry, but I didn’t have much choice. They were going
to upgrade us shortly if I didn’t pull the trigger myself. I figured
it was better to do it at a time of our chosing rather than have it
happen to us in a few days.


J.

On 7/04/2013 7:41 AM, Joel Uckelman wrote:

Thus spake Brent Easton:

Eclipse Users

As I have painfully discovered this morning, unless you are running the
latest (4.2 Juno) version of Eclipse, you will not be able to access the
new Sourceforge repository. Sourceforge uses version 1.7 of SVN which is
only available in Juno.

That’s annoying. Sorry, but I didn’t have much choice. They were going
to upgrade us shortly if I didn’t pull the trigger myself. I figured
it was better to do it at a time of our chosing rather than have it
happen to us in a few days.

All sorted now, wasn’t so bad.


Brent Easton
Analyst/Programmer
University of Western Sydney
Email: b.easton@exemail.com.au