Placing the Java API in a Maven repository about server

[zoharbabin]

@ratliff - Can you please provide more details about the process and what it entails?

Pushing the compiled client libraries to public library distributions is a longer term goal of the Continuous Integration Project.

You're help in implementing proper distribution for the Java client will be much appreciated.

Thanks

[ratliff]

You can either run your own Maven repository or submit your compiled code to the Maven central repository. If you run your own repository you can complete control over the distribution of your code. If you submit to the central repository, there may be terms and conditions.

Here is some information on submitting to the central repository through Sonatype http://central.sonatype.org/pages/ossrh-guide.html#deployment

Here is some information on using GitHub as a Maven repository http://blog.kaltepoth.de/posts/2010/09/06/github-maven-repositories.html

Or you can host the repository on your own server.

Once your libraries are in repository, I simply configure them in my pom.xml file. When anyone downloads and builds my code, Maven will automatically download the appropriate version of your Java library.

[jessp01]

Hi @ratliff,

We've actually made some progress from an infra standpoint since this was last discussed.
We now have this script which compiles the clientlibs and then runs the unittests:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/testAPI/test.sh
And also a build file for ant:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/build.xml

There is an automation generating clientlibs daily and pushing it onto the KalturaGeneratedAPIClients.* repos and a Travis hook on these repos to build and run the units [it calls testAPI/test.sh in the case of the Java client.

You can see the Travis runs here:
https://travis-ci.org/kaltura/KalturaGeneratedAPIClientsJava

We would be happy to use Maven for compiling and pushing it onto a Maven repo, hosted at the gh_pages of https://github.com/kaltura/KalturaGeneratedAPIClientsJava, similarly to what is described here:
http://blog.kaltepoth.de/posts/2010/09/06/github-maven-repositories.html

Would you be interested in creating a pom.xml to support this and making a pull request?
Thanks,

[ratliff]

Sure, I can have a go at it. May take me a few days.

From: Jess Portnoy <[email protected]mailto:[email protected]>
Reply-To: kaltura/server <[email protected]mailto:[email protected]>
Date: Tuesday, March 31, 2015 at 10:20 AM
To: kaltura/server <[email protected]mailto:[email protected]>
Cc: Mark Ratliff <[email protected]mailto:[email protected]>
Subject: Re: [server] Placing the Java API in a Maven repository (#1068)

Hi @ratliffhttps://github.com/ratliff,

We've actually made some progress from an infra standpoint since this was last discussed.
We now have this script which compiles the clientlibs and then runs the unittests:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/testAPI/test.sh
And also a build file for ant:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/build.xml

There is an automation generating clientlibs daily and pushing it onto the KalturaGeneratedAPIClients.* repos and a Travis hook on these repos to build and run the units [it calls testAPI/test.sh in the case of the Java client.

You can see the Travis runs here:
https://travis-ci.org/kaltura/KalturaGeneratedAPIClientsJava

We would be happy to use Maven for compiling and pushing it onto a Maven repo, hosted at the gh_pages of https://github.com/kaltura/KalturaGeneratedAPIClientsJava, similarly to what is described here:
http://blog.kaltepoth.de/posts/2010/09/06/github-maven-repositories.html

Would you be interested in creating a pom.xml to support this and making a pull request?
Thanks,

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1068#issuecomment-88105757.

[ratliff]

Neither your bash script nor your build.xml file will work for me. And some of the problems are fairly obvious (incorrect pathnames, etc).

Which branch of your repository should I be looking at? Jupiter-10.8.0 ???

Can we have a Skype call tomorrow morning to discuss?

From: Jess Portnoy <[email protected]mailto:[email protected]>
Reply-To: kaltura/server <[email protected]mailto:[email protected]>
Date: Tuesday, March 31, 2015 at 10:20 AM
To: kaltura/server <[email protected]mailto:[email protected]>
Cc: Mark Ratliff <[email protected]mailto:[email protected]>
Subject: Re: [server] Placing the Java API in a Maven repository (#1068)

Hi @ratliffhttps://github.com/ratliff,

We've actually made some progress from an infra standpoint since this was last discussed.
We now have this script which compiles the clientlibs and then runs the unittests:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/testAPI/test.sh
And also a build file for ant:
https://github.com/kaltura/server/blob/Jupiter-10.8.0/generator/sources/java/build.xml

There is an automation generating clientlibs daily and pushing it onto the KalturaGeneratedAPIClients.* repos and a Travis hook on these repos to build and run the units [it calls testAPI/test.sh in the case of the Java client.

You can see the Travis runs here:
https://travis-ci.org/kaltura/KalturaGeneratedAPIClientsJava

We would be happy to use Maven for compiling and pushing it onto a Maven repo, hosted at the gh_pages of https://github.com/kaltura/KalturaGeneratedAPIClientsJava, similarly to what is described here:
http://blog.kaltepoth.de/posts/2010/09/06/github-maven-repositories.html

Would you be interested in creating a pom.xml to support this and making a pull request?
Thanks,

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1068#issuecomment-88105757.

[jessp01]

Closing as this discussion resulted in this pull request:
#2397

Mark, thank you, I am testing the code generation from your clone now.