Github releases
by Lucas Holmquist
Hi all,
yup, sending this on a Friday, at 3pm EST.
while going over some of the JS push tutorial docs, i found that the links to the AG JS lib were point to somewhat older releases. While we could try to remember to update these docs after every release, i propose we use githubs really neat “release” button.
Basically, we would still tag our releases normally, and after we push those up, we can press the “Draft a New Release” button.
This allows us to choose an existing tag, but some release notes in, and also mark as a pre-release
but the best part, is that we can now link to the “latest” release in our docs
This is the link created: https://github.com/aerogear/aerogear-js-dist/releases/latest
this will link to: https://github.com/aerogear/aerogear-js/releases/tag/1.5.1
wdyt?
-Luke
11 years, 9 months
UPS build
by Bruno Oliveira
Guys, is just me or the UPS build became crazily slow?
--
abstractj
PGP: 0x84DC9914
11 years, 10 months
Android Registrations
by Summers Pittman
We've mentioned moving from the factory/producer/headache pattern that
we currently use (Pipeline, etc) to something more fluent and more
maintainable. See this JIRA : https://issues.jboss.org/browse/AGDROID-259
To that end I've stubbed out some classes and made a strawman set of
unit tests for Pipeline :
https://gist.github.com/secondsun/8478a5f0527fc97b2456
In the comments of some of the tests I've added questions for the
implementation portion of Registrations.
The ultimate goal is to make the factories and feature classes(Pipe,
AuthModule, etc) flexible enough that circular dependencies can be
broken and 1) modularization can happen and 2) feature additions can be
quicker and change fewer stable APIs.
Comments, questions, and tomatoes are welcome.
--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
11 years, 10 months
[Android] UnifiedPush Registration as a separate module ?
by Sebastien Blanc
Hi !
This is just an idea (for later/future) I had when I looked at the Amazon
Device Messaging bits (the GCM variant from Amazon).
Basically it's just Java/Android code :
https://developer.amazon.com/public/apis/engage/device-messaging/tech-doc...
But when we will implement the UPS Amazon library there will be some
duplication (basically the UPS registration process).
It would be nice if this was extracted into a small module (i.e :
android-unifiedpush-registration) that could be used by the "pure" android
bits (i.e : android-unifiedpush-gcm) and by the Amazon bits
(android-unifiedpush-adm) and maybe later by other system based on Android
but using their own Push infra.
wdyt ?
Sebi
11 years, 10 months
