RHEL, SLES

See https://github.com/mariadb-corporation/MariaDBEnterprise-Team-box/tree/master/packaging/mariadb-java-client/rpm for initial effort.

kolbe thanks for having created this. It's now one of the priority idea for the Connector/J, list which is here now : https://docs.google.com/document/d/1QnjjoXFo2ni0rTWpQ0fhIMaDT91BV5cOOMre7xq9b9A/edit# So I linked it to the task.
I have been told that this is an important thing Amazon is expecting next from us, this is why it's a top priority. But this will be discussed with the SEs, Consultant and Sales next to be confirmed.

I have several questions for you :
1. For Amazon, I guess that users will use various OS, what shall we do : Yum only as per the task title, Apt as well ?
2. Should we target to support only few OS, or all ? I see RHEL and SLES in your task definition, is that the target scope ?
3. I recall you asked how to manage our repos / token, which Amazon. Have you had any more info or insight from Amazon ?

Let's support all of our supported MariaDB Enterprise OSes for our Connector packages.

This is not exactly the right place to mention it, but we should probably also start officially supporting Amazon Linux given our evolving relationship there. We should be sure to test our packaging and install processes there.

Nothing new wrt tokens & Amazon, though I'm not sure what exactly you're referring to.

So so the target is feasible really to support all of our supported MariaDB Enterprise OSes on one go as part of the next release, or do you foresee some steps to get there ?

As for the the token / Amazon question, since the Connectors packages will be using our token, how are the Amazon users getting those from us : what is the workflow ? I recall you had questions, relevant ones related to it.

As for the proposition to support officially Amazon Linux I agree. I'll have that created as a task and added to our backlog for Phase 5.
https://mariadb.atlassian.net/browse/ME-401

pcrews could you invest next week half a day on this and try to estimate, specify this and share it with kolbe and I please ? ratzpo would it be possible to ask Otto to help on this as well please ? We don't want to invest time on packaging unless we are pretty clear on what to do, see the time we lost on PGO recently and in the past.

pcrews, if you have any ideas about the most natural path to take for building RPMs and .debs of our Java connector, that's great. If you don't, maybe you could do a half day of research to see what you come up with. If that returns something positive, great. If not, OK. I just want to try to dig into this to see what it will take to create proper packages of our connectors, starting with Connector/J. Let me know if you have any questions.

Since there is no dependencies and since pcrews is in OSCON this week diego dupin and I agreed that diego dupin will to try first and pass to pcrews after if needed. I"ll ask ratzpo for Otto as well in case of

I begin to test the different maven plugins to create rpm and yum packaging.
first step done : script the fat-jar creation (the driver AND the additionnal dependencies in one jar) with http://maven.apache.org/plugins/maven-shade-plugin/index.html
now testing packaging script with the maven plugins (rpm-maven-plugin)

I will send the result package to check if it's valid.

I've used the fat-jar approched : the .jar contain the jna and slf4j dependencies.

Packaging goal:

• install the fat-jar "mariadb-java-client-1.2.1.jar" in /usr/share/java
• create a symbolic link "/usr/share/java/mariadb-connector-java.jar" pointing to "mariadb-java-client-1.2.1.jar"
• install /usr/share/doc/mariadb-connector-java/copyright file

I've added maven plugins so when packaging for a maven release, additionnal files for unix packaging will be generated.
Here are the packaging files generated with maven plugins.
using plugins [https://github.com/tcurdt/jdeb|jeb] to generating .deb :

• mariadb-java-client_1.2.1_all.changes
• mariadb-java-client_1.2.1_all.deb

Using plugins [http://www.mojohaus.org/rpm-maven-plugin/|rpm-maven-plugin] to generate rpm files :

• mariadb-java-client.spec
• mariadb-java-client-1.2.1-1.noarch.rpm

(those files are not signed)

I'm a beginner in unix packaging, so i've test what i can.
In packaging, an email is mandatory, so i put mariadb@mariadb.com. Is there any email i can use for that ?
Patrick can you check the generated files to see if anything wrong or missing ?

pcrews Diego never got your feedback on that, have you had time to review this ?

marked as won't do for now, since pending for 5 years