SVN Build, Do It Yourself

[Braids]

see my post at http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=3721&p=64847#p64850 for the missing file and a plea to put the scripts under svn so we can maintain them properly.

[UnderFlow]

I'm not sure if Underflow's scripts are working as they should. I work on Windows XP, so robocopy doesn't get recognized as a valid command, and I don't get a run-forge.jar file or a forge.exe file. Is there a working version of a script that will do the trick?

Xp doesn't come with robocopy. You can either manually revert the script to use xcopy or download robocopy (see Hellfish's last posts in this thread).


As for the exception: I am getting similar exceptions, but don't know what causes them. Maybe some library problems again, but it doesn't look like it. :/

[Sloth]

see my post at http://www.slightlymagic.net/forum/viewtopic.php?f=52&t=3721&p=64847#p64850 for the missing file and a plea to put the scripts under svn so we can maintain them properly.

I agree, we should upload it.

As for the exception: I am getting similar exceptions, but don't know what causes them. Maybe some library problems again, but it doesn't look like it. :/

Can you commit to the SVN UnderFlow? Should I upload the script to the SVN? Which version should I chose?

EDIT: When I use my version of the script the CardList (and AbilityFactory_Attach) class won't be compiled (problem with yield). Is this the same problem you have?

[Snacko]

I don't see a point in including them into svn as you should use the maven or eclipse if you can already access the repository.

[UnderFlow]

Can you commit to the SVN UnderFlow? Should I upload the script to the SVN? Which version should I chose?

EDIT: When I use my version of the script the CardList (and AbilityFactory_Attach) class won't be compiled (problem with yield). Is this the same problem you have?

1. Nope, I have problems with my gmail account atm, I'll work on it tomorrow.
2. Feel free to add it to the SVN. I'd use the most recent version of the script (1.3) and include all the other files that are needed too.
3. Yes, that sounds like our problem.

[Braids]

I don't see a point in including them into svn as you should use the maven or eclipse if you can already access the repository.

the point of putting them into svn is to make them easier to maintain them and to have a centralized repository for the latest versions.

i like our bleeding edge testers, and i want to be nice to them.

[Sloth]

I don't see a point in including them into svn as you should use the maven or eclipse if you can already access the repository.

Our beta testers (and lazy people like me) should be able to compile without setting up a workspace and sorting libraries to test the newest version.

2. Feel free to add it to the SVN. I'd use the most recent version of the script (1.3) and include all the other files that are needed too.

I don't think we can just put all the build files on the SVN. We can have the script on the SVN, but the content of the zip file is mostly licensed stuff.

[goonjamin]

If you keep the script only (build-forge.bat) on the SVN could the run.bat script in the zip file be updated to do the svn update (I can't see this command needing to be updated very often)? Then you could just change the path it uses to run build-forge.bat to run whatever the most recent build script that was just downloaded in the svn update?

That way you can keep the part that needs more updates on the SVN and the rest of the licensed stuff in the zip on the forum here as you have it now.

[Braids]

I don't think we can just put all the build files on the SVN. We can have the script on the SVN, but the content of the zip file is mostly licensed stuff.

i'm only advocating for modifiable (text) files for being placed into svn.

[Sloth]

OK. I've added Underflows version 1.3 of the script to the SVN.

If you keep the script only (build-forge.bat) on the SVN could the run.bat script in the zip file be updated to do the svn update (I can't see this command needing to be updated very often)? Then you could just change the path it uses to run build-forge.bat to run whatever the most recent build script that was just downloaded in the svn update?

That way you can keep the part that needs more updates on the SVN and the rest of the licensed stuff in the zip on the forum here as you have it now.

Even if the compiling fails, the updating from svn will work and you will get the newest build-forge.bat.

[UnderFlow]

If you keep the script only (build-forge.bat) on the SVN could the run.bat script in the zip file be updated to do the svn update (I can't see this command needing to be updated very often)? Then you could just change the path it uses to run build-forge.bat to run whatever the most recent build script that was just downloaded in the svn update?

That way you can keep the part that needs more updates on the SVN and the rest of the licensed stuff in the zip on the forum here as you have it now.

That would probably make things complicated, but it is technically easy. I'll put it on my TODO list.

And if the content of the zip could cause trouble, we should not put it in the SVN; most people will get their version from the forum anyway.

[Braids]

i already see a bug in the build-forge.bat. in section two, where the line starts with

java -jar build\ecj-3.5.2.jar forge-svn\src -1.5 -classpath

i think the {-1.5} should now be a {-1.6}. or {-6}, i'm not sure.

[Sloth]

i already see a bug in the build-forge.bat. in section two, where the line starts with

java -jar build\ecj-3.5.2.jar forge-svn\src -1.5 -classpath

i think the {-1.5} should now be a {-1.6}. or {-6}, i'm not sure.

That was the error. Good catch Braids.

[Braids]

i think the {-1.5} should now be a {-1.6}. or {-6}, i'm not sure.

That was the error. Good catch Braids.

yippee! thanks! i'm not familiar with the jar file it was executing, and i didn't want to have the responsibility of testing it, so i just posted instead.

one question. what is the error?

[UnderFlow]

Thanks, Braids. Fixed in script version 1.4.

Also, I added a few lines to run.bat to make it update build-forge.bat, like goonjamin suggested.

Lastly, since there were some people with locking issues, I added the cleanup script to the zip package.

http://dl.dropbox.com/u/5988273/forge-build.zip

http://dl.dropbox.com/u/5988273/build-forge.bat
http://dl.dropbox.com/u/5988273/run.bat
http://dl.dropbox.com/u/5988273/cleanup.bat