#146 Deploy to Public Maven Repository

[lessonz]

Possible duplicate of https://sourceforge.net/tracker/?func=detail&aid=2975844&group_id=37202&atid=419489 In that issue, pavelsavara appears to have manually deployed the then current version of robocode.api. Better might be to have the project configured to deploy to your repo, http://robocode.sourceforge.net/maven2/ It would be awesome if robocode was deployed to a public repo. This would allow robocoders to become familiar with build tools such as Maven, Ant+Ivy, etc.

Cheers.

[lessonz]

Also, this maven plugin: http://mojo.codehaus.org/versions-maven-plugin/update-child-modules-mojo.html might be useful in dealing with the versioning issue. I believe it should allow you to only have to update the version number in one place. (This also might help with the move to Maven 3.)

[Michel Jung]

I could set up a complete build environment including deployment to maven central for you, if you want me to.

[Flemming N. Larsen]

HI Michel Jung. You are very welcome to set up an environment for Robocode to the maven central. That would be great.

The sources are available here at GitHub:
https://github.com/robo-code/robocode

Each project/module has a pom.xml file, and the "super pom" is located inside the \super-pom directory at the root. :-)

[lessonz]

I would love to see this. At one point in time, and I had tried to do similar, but my builds failed probably because I was using Maven 3, but I really didn't try to troubleshoot as I got pulled off onto other things. But, this would still be great.

[Michel Jung]

Well then, give me a few days and I'll set things up :-)

[lessonz]

I've never used https://bintray.com/ but it might be perfect for something like this.

[Gerard de Leeuw]

Is there any status update on this?
I would really like to be able to access the robocode API via Maven Central.

Alternatively I could alter the pom.xml files in the current GitHub repository for automatic uploading to Maven Central (by hosting it on the Sonatype OSS nexus).

For some resources see:
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven

[Michel Jung]

I started with that, but there are some issues; Robocode uses artifacts that are not in maven central. All these artifacts need to be deployed to maven central first (at least runtime dependencies, build dependencies shouldn't be necessary).

[Gerard de Leeuw]

Which artifacts are you referring to? I could find every artifact that is used by Robocode in Maven Central. The only (external) artifact that is not in there is net.sf.robocode:codesize:1.1, but since that is also part of the Robocode project you might as well upload it too.

Edit: Codesize is actually already in Maven Central

[Michel Jung]

Yeah I migrated codesize so it's now in maven central. But jni4net, for example, isn't. Just remove all <repositories> entries from all POMs in robocode and you'll see which artifacts are missing. However, you need to have all maven plugins in your local repository to be able to build the project.

[Gerard de Leeuw]

Ah, my bad in that case. I didn't look in the dotnet part of the sources, so I get what your are referring to.

Are you planning to upload everything to Maven Central at once? Otherwise you could maybe only upload the Java part of Robocode. I geuss the API is what most Maven users are interested in anyway.

[Anonymous]

If all dependencies of the java part are in maven central, then yes, it would be possible to upload it. I don't have much time right now, but if you could verify that, I could do the upload.