SVN is ready - DO NOT USE GITORIOUS

[Chris H.]

I'll give the work around a try tonight and thanks for taking the time to get back to me.

`
If you are still having problems building the archive you can try another approach. Check out this link:

The SVN, nightly builds and biweekly betas

[goonjamin]

Thanks Chris.

I didn't have time yesterday to try manually setting the version number but if that fails I will just start grabbing the nightly build instead.

[Chris H.]

I added some instructions to the getting started wiki in refence to the Maven commands that perform the Nightly Build and the Bi-Weekly beta releases.

[Doublestrike]

I'm getting this error continuously when I try to import the Maven project:

Code: Select all

RA layer request failed
svn: REPORT of '/forge/!svn/vcc/default': Could not read response body: connection was closed by server (http://svn.slightlymagic.net)

The same error appears if I use "File->Import->Maven->Check Out Maven Projects from SCM" or "File->Import->SVN->Checkout Projects from SVN".

As recommended in this thread, I'm using http://svn.slightlymagic.net/forge/trunk.

The progress quits at random places (I've tried it several times).

Working from a clean install, extra software can be seen in attached pic.

Can someone point me in the right direction? I assume I can do this via a command prompt, but I don't have the pom.xml either...

[Braids]

I'm getting this error continuously when I try to import the Maven project . . .

except for the first Maven build, developers typically don't need to touch maven. have you checked out a working copy using Subclipse? File, Import, SVN, Checkout Projects from SVN, Next >, . . .

[Chris H.]

Have you tried the getting started wiki?

As Braids suggests,

checked out a working copy using Subclipse? File, Import, SVN, Checkout Projects from SVN, Next >, . . .

should get the project on onto your computer. Once you have the project you should be able to use the CLI as needed.

We recently switched from Git to SVN and as such most people can ignore most of the Maven stuff. With the SVN the Maven stuff is pretty much build and release and this is not needed for most of the ongoing dev work.

[Braids]

. . . We recently switched from Git to SVN and as such most people can ignore most of the Maven stuff. With the SVN the Maven stuff is pretty much build and release and this is not needed for most of the ongoing dev work.

do people still get those 400+ compiler errors until they run the first maven build?

[Chris H.]

do people still get those 400+ compiler errors until they run the first maven build?

`
A few times over the last week I saw some errors and I believe that I saw some activity in the lower right corner of Eclipse.

This morning I did a Nightly Build and afterwards I noticed 66 errors but they went away and disappeared. I keep Eclipse set to Build Automatically.

[Doublestrike]

Thanks for the info - I do get the same error with the SVN import as well.

In the past, I recall I had trouble with \build\manifest.forge. I'd switched to Maven as recommended in this thread.

But now no more Maven Anyway I learned something if there's a switch back.

Update 1
I've tried again about 10 times and I'm getting consistently kicked off the server when the directory changes. This looks to be a connection problem (http://lists.freepascal.org/lists/fpc-devel/2009-July/017007.html).

Update 2
Now using repeat command line requests

Code: Select all

svn checkout http://svn.slightlymagic.net/forge/trunk -r HEAD --depth=infinity --force

This method works better since when a request breaks, the next request picks up where the last one stopped. Subclipse starts over from the beginning. Not sure why this happens.

Usually error message reads something like "connection was closed by server". Sometimes will get "connection forcibly closed by server". These errors happen when a directory change is requested, not on a file download.

Update 3
Confirmed. The command above successfully checked out a revision piece by piece. A little intensive since the checkout must be restarted every time it's broken, but it works if nothing else does. Subclipse not recommended for this situation.

============

Still several things I'll be trying today and tomorrow, suggestions welcome.

[Braids]

. . . Confirmed. The command above successfully checked out a revision piece by piece. A little intensive since the checkout must be restarted every time it's broken, but it works if nothing else does. Subclipse not recommended for this situation.

i had very similar troubles with google's svn. i hope you can (svn update) without connection errors!

edit: oh, and don't use svn branches if you are having these kinds of errors. {you would know if you were using one.} if you need a private branch, i would recommend using git-svn, storing the branch on your own computer and keeping it updated with git-svn.

[Chris H.]

Update 3
Confirmed. The command above successfully checked out a revision piece by piece. A little intensive since the checkout must be restarted every time it's broken, but it works if nothing else does. Subclipse not recommended for this situation.

============

Still several things I'll be trying today and tomorrow, suggestions welcome.

`
Have you been able to get the entire project checked out yet?

[Doublestrike]

Have you been able to get the entire project checked out yet?

Yes, using the command line method. (I'm still curious why that version will pick up where it left off, but Subclipse deletes all and starts over.)

There's a few other variables I'll be playing with over time to see if there's a better solution: a) I'm currently in China so the connection could be doing weird things I don't know about and b) my dev environment runs off a USB stick, which may cause hiccups somewhere in the process.

Either way, today I'll try a build (http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=1093&start=45#p48823) and maybe attack a bug. On to bigger and better things.

[Braids]

i nearly missed this because it was an edit!

. . . (Incidentally, I'd be happy to be the wiki guy if y'all need one. I think quick, easy documentation is important. As I'm slowly sifting through these years of threads, it would be good if I could publish what's relevant.)

that's great! go for it! as far as i'm concerned, it's a wiki. everybody can edit. just login to the wiki with your forum name & password, and you can edit pages. try to keep the style if you can. we typically use bold for buttons and things to click, which means we surround the phrase with three apostrophes. the Forge wiki uses the wikimedia syntax, same syntax as wikipedia.

you might want to post before you're about to make changes, and for how long you think you'll be editing which document.

[goonjamin]

Sorry for the long delay but I just tried again with a clean r9842 checkout and I still get the same error on my machine. I went in and forced the version number as suggested in the pom.xml and everything works fine after that.

I updated to r9793 and am still getting the same launch4j error? I have attached a full copy of the error in the attached. Also in case it is important I am running windows 7 32bit.

Unfortunately, I am not able to replicate the error. I use Windows XP in a virtual machine. I ran it from the command line and from Eclipse without issue. I keep looking but I am not optimistic. As a workaround look in the pom.xml file and find the "${releasedVersion}.0" lines. You can put the version number in explicitly (such as 1.12.0.0) and it should work. For some reason the variable is not resolving.

[Doublestrike]

i nearly missed this because it was an edit!

Yeah, not quite sure where I stand since I'm new to the community. Took that line out since I felt "who am I to tell you guys what to do". But if you don't mind, then I'll jump in. Thanks for the help!

BTW is there an API for the flavor of BBCode markup used in CCGH?

Update

Yes, there is: http://www.mediawiki.org/wiki/Help:Editing