Good morning peeps.
AeroGear Security 1.2.0 was staged under nexus profile
- Instructions to test it
* Download the sources from
* run mvn clean package and deploy it
* Make use of these sources to send a request against the server:
* [maven-release-plugin] prepare for next development iteration
* [maven-release-plugin] prepare release 1.2.0
* Revert "Preparing to release AeroGear Security 1.2.0"
* Merge branch 'parent_pom'
* remove stuff provided by the parent pom
* add aerogear's parent pom
* fix pom formatting
* Preparing to release AeroGear Security 1.2.0
* Merge branch 'hawk'
* Le missing license headers
* Inclusion of Javadocs for Hawk
* Update to Hawk 1.0.0
* Fix the error messages
* Handle more generic exceptions
* Follow the header conventions from Hawk
* Hawk server configuration must be provided by the developer
* Fix the issues with Hawk and CDI
* Merge branch 'formatting'
* fix formatting
* Merge branch 'license_fixes'
* fix license headers
* Merge branch 'JavaDocForSecure'
* Removing stupid import (thanks Eclipse)
* Fixing typos
* Adding an XML example...
* Adding JAvaDoc for the Secure annotation + Hint on enabling in
projects beans.xml file
* Update README
Feedback, suggestions to improve the documentation, tomatoes are
welcome. On wednesday I'll send it to maven central, so if you would
like to test, let me know.
I'm looking to make an Android push-enabled QuickStart to demonstrate the push server on OpenShift. I was initially going to implement this on the TODO application, but it looks like that will likely be removed.
Do you have any suggestions for a QuickStart that I could tackle that could be used to demonstrate the push server on OpenShift?
one of the possible ways how to fix OpenShift cartridge going idle could be
fixed by deploying the backend to the cartridge right before tests. That way
it would be fresh when running tests.
There is already tooling almost exactly what we need. However, it
would "polute" Aerogear JS with some WAR or whatever Kris needs to be deployed.
I'm now trying the unified push with Android and I've noticed, that there is no way (or I didn't find it?) to unregister the device. Example real usage: in application settings there might be a checkbox to disable notifications, so the user probably won't like receiving push messages which would then be discarded by the device (it'd be a waste of his data package). It seems to me like it wasn't left out on purpose, but rather forgotten to be added. Any thoughts on this?
I'm preparing additional site trackers for RHT's marketing team, and
will need to put it live for them to verify if we're doing it right.
So, master will be unstable for a little bit, so please refrain from
pushing to prod at least for the next two days (I'll try to sort this