Dario Romano

The video is now live here. It can be found at the end of the article. The video is not listed on youtube and should be only visible to those who have the link or those who watch it on the website.

The video is now live here. The video is not listed on youtube and should be only visible to those who have the link or those who watch it on the website.

Yes, since I will be showing footage from robocode matches in the demo, I sure wanted to give it some credit. If you are ok with this, I will also mention you in the outro for helping me set robocode up. If you want I could also add a link to the robocode website / wiki ?

Hello! Now that I have modified robocode to work with the runtime monitoring framework, I would like to use robocode to produce a short demonstrator video for the tool using robocode. I wanted to ask, if there are any images I am allowed to use in this demonstration video, like the robocode logo that is shown in the game when no battle is active, or any other representative logo for robocode. Cheers Dario Romano

Hello Larsen! After fiddling around a bit, and changing a few paths in the build.xml in ExternalToolBuilders to match my local directories it now seems that everything works correctly! Thank you for your help, I wouldn't have managed by myself. Just to give you an idea what I'm no planning to do with robocode now that it's running: I'm going to inject probes to do requirements checking during runtime on an external framework. Basically what it should do is, to check if any game-rules are broken during...

I tried running Robocode like you described, but as you anticipated, it runs into an error, that the launch directory does not exist. When trying to clean the project I'm running into anothe rissue. The build seems to be missing a directory that does not show up in the eclipse package explorer, but does exist when I browse there by using the windows explorer. Here a screenshot: I'm just a bit confused of why the folder is there physically, but is not being recognized by eclipse.

With the new updates in the project mvnassembly now succeeds in building. The POM files still get shown as having an error in eclipse, but since the assembly from command line works, i suppose it doesn't hurt much. Is the eclipse built in maven support even supposed to work, or is it designed to be built by calling mvnassembly manually via the command line? If it's still of any help, for this try I have installed Maven 3.5.2 to use globally, so my mvn --version prints this: C:\>mvn --version C:\...

With the new updates in the project mvnassembly now succeeds in building. The POM files still get shown as having an error in eclipse, but since the assembly from command line works, i suppose it doesn't hurt much. Is the eclipse built in maven support even supposed to work, or is it designed to be built by calling mvnassembly manually via the command line? If it's still of any help, for this try I have installed Maven 3.5.2 to use globally, so my mvn --version prints this: ´´´ C:>mvn --version C:\...