Maven support

[jjzazuet]

Hello again. One more question.

Are there any plans to upload the engine's binary distribution as Maven artifacts at the central repo or some other MAven repository?

Thanks!

[jerome_j]

We currently don't plan to distribute our binaries outside our website/server.

I can give a look to set up a maven repository here. Did you have a good doc for setting up a maven repository ?

[jjzazuet]

Hello again. Sorry for the late reply .

Quoting from this article

http://outofsingularity.wordpress.com/2011/05/15/create-custom-maven-repository-to-store-artifacts-unavailable-in-general-maven-repositories/

Two ways:

1) This one's a bit rudimentary but it only requires a web server:

http://www.javaworld.com/community/node/3968

2) Setting up a custom Nexus instance on your domain. It's a bit more contrived, but equally robust as well.

http://www.sonatype.org/nexus/

Let me know if may be of further assistance.

Thanks!

[jerome_j]

Thanks, the 1'st way was helpfull for the deployment.

I've deployed for testing purpose the last dev build (aka 1.3.1 24-08-2012) under the maven version VERSION_ID.
Seems to works fine from here, let me know if it's ok:

As soon as the maven deployment will be integrated in our build machine, next build will be deployed with proper versioning in this new maven repo.

[jjzazuet]

Yep. I think it works fine!

Here's my example test project pom.xml and the build log (Maven 3).

Let me know if there's anything else I could do or specify in the meantime.

Thank you so much for your time and help!

Example pom.xml


Build log:

[jjzazuet]

Hello. Jesús again.

Now that we have proof that the preliminary Maven repo structure works, I'm guessing the next version to  be uploaded to this repo structure (i.e. with correct version numbers) will come after 1.3.1 24-08-2012 right?

Or would it be possible to retag 1.3.1 dev in the repo meanwhile?

Let me know if there's anything else I could do or specify in the meantime.

Thanks for your time and help!

JZM

[jerome_j]

Yes, I'll upload all next versions in the maven repo with version number. Next build will be 1.3.1 branch planned for late october. Until then, the maven repo will stay like this.

[jjzazuet]

Awesome! Thanks! 

[jerome_j]

For those who have problems with maven repository, some jars was not committed in the repository.
This has been just fixed. The maven repository has been resetted and contains the build 1.3.1-13-04-2013 (and will receive all next dev/stable builds).