Re: [aerogear-dev] [Vote] UPS 1.0.3 release

Hi, we tagged for UPS 1.0.3, and I did upload the JAR files to NEXUS, but I am not yet able to create a staging repo for that (I notified our ops team). However, for testing the server, all we really need are the WAR files. I have uploaded the distribution files to GH, as a pre-release: https://github.com/aerogear/aerogear-unifiedpush-server/releases/tag/1.0.3 <https://gist.github.com/matzew/a5ada653c1e13b4b55cc#notes>NOTES 1. We no longer support H2 database. You need MySQL/Postgres for tests. 2. The JPA provider no longer creates the DB schema for you If you don't have MySQL installed, it's trivial to use it via Docker: docker run --name unifiedpushDB -p 3306:3306 -e MYSQL_USER=unifiedpush -e MYSQL_PASSWORD=unifiedpush -e MYSQL_DATABASE=unifiedpush -e MYSQL_ROOT_PASSWORD=supersecret -d mysql Now, once the DB is up, you need to run the migrator against the empty database to create the schema. The migrator is included in the dist file, and instructions are here <https://github.com/aerogear/aerogear-unifiedpush-server/blob/1.0.x/migrat... DB setup for EAP/WildFly works as usual, see https://aerogear.org/docs/unifiedpush/ups_userguide/index/#gendbds Once that is all done, install the WARs to your application container: https://aerogear.org/docs/unifiedpush/ups_userguide/index/#deploy Let me know about this release, and if there are no complains by Wednesday, I will push the bits to maven central and mark the pre-release as a real release Oh, this is most-likely the last release of the 1.0.x series -Matthias PS: I am now updating the docs, to reflect the changes and new requirements -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf