Aerogear Test BOM updates
by Karel Piwko
Hi,
I've updated test dependencies in Aerogear Test BOM,
https://github.com/aerogear/aerogear-parent/pull/10. It's time for QE
to maintain dependency versions at the same place ;-)
While this does not represent a full set of dependencies we use yet, it
would be handy to have it in 0.2.3 or 0.3.0 release of Aerogear BOM.
Is there such release planned?
Thanks,
Karel
10 years, 3 months
broken build (master and 0.11.0 tag)
by Matthias Wessendorf
Hi,
since Friday, all in a sudden, the node.js part of the build (triggered by
the frontend plugin inside the 'server' module) is failing on different
ways.
Extremely odd: the 0.11.0 tag is effected as well. The release (on maven
central) is good, but ATM we are not able to build the source on the 0.11.0
tag :-(
Oh, yeah, Travis-CI notice the broken build as well ;-) and thankfully
abstractj put in a PR to have a temporary fix for the build failure:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/293
Thanks Bruno!
Yesterday Bruno, Villiam and Luke looked at this already, and they noticed
a failure like this:
[INFO] --- frontend-maven-plugin:0.0.15:npm (npm install) @
unifiedpush-server ---
[INFO] Running 'npm install --color=false' in
/home/travis/build/aerogear/aerogear-unifiedpush-server/admin-ui
[INFO] npm WARN package.json newadmin(a)0.0.0 No repository field.
[INFO]
[INFO] --- frontend-maven-plugin:0.0.15:grunt (grunt build) @
unifiedpush-server ---
[INFO] Running 'grunt dist --no-color' in
/home/travis/build/aerogear/aerogear-unifiedpush-server/admin-ui
[INFO] >> Local Npm module "grunt-cli" not found. Is it installed?
[INFO]
[INFO] Running "bower:install" (bower) task
[INFO] Fatal error: Arguments to path.join must be strings
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
Note: "grunt-cli" *IS* installed, even globally. If I am correct, at the
moment we are not 100% sure what the "Fatal error: Arguments to path.join
must be strings" really means...
On my machine, I noticed the npm stuff downloads half of the internet, but
gets stuck in the middle:
[INFO] npm http 304 https://registry.npmjs.org/oauth-sign
[INFO] npm http 304 https://registry.npmjs.org/aws-sign2
[INFO] npm http 304 https://registry.npmjs.org/hawk
[INFO] npm http GET https://registry.npmjs.org/combined-stream
[INFO] npm http GET https://registry.npmjs.org/async
[INFO] npm http GET https://registry.npmjs.org/assert-plus
[INFO] npm http GET https://registry.npmjs.org/asn1
[INFO] npm http GET https://registry.npmjs.org/ctype
[INFO] npm http GET https://registry.npmjs.org/punycode
[INFO] npm http GET https://registry.npmjs.org/hoek
[INFO] npm http GET https://registry.npmjs.org/boom
[INFO] npm http GET https://registry.npmjs.org/sntp
[INFO] npm http GET https://registry.npmjs.org/cryptiles
[INFO] npm http 304 https://registry.npmjs.org/async
[INFO] npm http 304 https://registry.npmjs.org/combined-stream
[INFO] npm http 304 https://registry.npmjs.org/assert-plus
[INFO] npm http 304 https://registry.npmjs.org/asn1
[INFO] npm http GET https://registry.npmjs.org/delayed-stream
[INFO] npm http 304 https://registry.npmjs.org/ctype
[INFO] npm http 304 https://registry.npmjs.org/punycode
[INFO] npm http 304 https://registry.npmjs.org/boom
[INFO] npm http 304 https://registry.npmjs.org/hoek
[INFO] npm http 304 https://registry.npmjs.org/cryptiles
[INFO] npm http 304 https://registry.npmjs.org/sntp
[INFO] npm http 304 https://registry.npmjs.org/delayed-stream
Now, after more than one hour of 'waiting', I cancled the build, resulting
in:
[INFO] > optipng-bin(a)0.3.9 postinstall
/Users/matzew/Work/JBoss/UPS/admin-ui/node_modules/grunt-contrib-imagemin/node_modules/imagemin/node_modules/imagemin-optipng/node_modules/optipng-bin
[INFO] > node index.js
[INFO]
[INFO] ✓ pre-build test passed successfully
[INFO] npm http 304 https://registry.npmjs.org/hoek
[INFO] npm http 304 https://registry.npmjs.org/boom
[INFO] npm http 304 https://registry.npmjs.org/cryptiles
[INFO] npm http 304 https://registry.npmjs.org/sntp
[INFO] npm http 304 https://registry.npmjs.org/delayed-stream
^C[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] AeroGear UnifiedPush Server ....................... SUCCESS [3.884s]
[INFO] UnifiedPush Model Layer ........................... SUCCESS [0.146s]
[INFO] UnifiedPush Server Model API ...................... SUCCESS [2.699s]
[INFO] UnifiedPush Server Model JPA implementation ....... SUCCESS [15.036s]
[INFO] UnifiedPush Service Layer ......................... SUCCESS [7.757s]
[INFO] UnifiedPush Push Notification Networks ............ SUCCESS [2.009s]
[INFO] UnifiedPush RESTful Endpoint ...................... SUCCESS [2.811s]
[INFO] UnifiedPush Server (WAR) .......................... FAILURE
[1:30:54.769s]
[INFO] UnifiedPush Auth Server ........................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:31:29.994s
[INFO] Finished at: Tue Jul 15 07:48:37 CEST 2014
[INFO] Final Memory: 80M/191M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
com.github.eirslett:frontend-maven-plugin:0.0.15:npm (npm install) on
project unifiedpush-server: 'npm install --color=false' failed. (error
code 130) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with
the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <goals> -rf :unifiedpush-server
This is more a FYI on what's going on - I will file a JIRA ticket for that;
*PS:* According to yesterday's IRC discussions, a manual `grunt server does
work, so development is not*directly* effected
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
10 years, 3 months
AeroGear Cordova Push Plugin: Device Token before registry
by Chau Thai
Dear AeroGear developers,
I'm building a geo based push system and want to use the device token as
the alias in the registration process.
I noticed there is no way to get the device token with the AeroGear
Cordova Push Plugin before you send the registration request to the server.
I'm hacking into the Android Plugin at the moment and would be very glad
if you could give me some hints to get the device token, since the libs
are all in jars...
Thanks
Chau/Cydmax
--
Chau Thai
BLIPhead GmbH
Paradiesstr. 9
80538 München
Tel +49 89 21111069
Fax +49 89 21111061
Mobil +49 176 70660664
chau(a)bliphead.com
www.spreya.com
Geschäftsführer: Michael Mühlberger
Amtsgericht München, HRB 190699
10 years, 3 months
SimplePush Server 0.12.0
by Daniel Bevenius
I've moved the release of SimplePush Server 0.12.0 to August instead of
July. There were only about four tickets for this release not all effected
the server at all really (Docker and docs are examples).
I've instead moved the release to August and will move some task targeted
for "future". I've already moved the SockJS[1] but let me know if there are
any tasks you'd like to see in the release.
I've updated the roadmap in this pr:
https://github.com/aerogear/aerogear.org/pull/320
Thanks,
/Dan
[1] https://issues.jboss.org/browse/AGSMPLPUSH-30
10 years, 3 months
pushplugin release
by Erik Jan de Wit
Hi,
After succeful testing I’m happy to announce that the 0.6.0 version of the aerogear-pushplugin has been released. Thanks to everyone involved in making this release happen.
Bug
[AGCORDOVA-16] - Should fail gracefully if not configured
fix a bug with the foreground/isInline flag
fix bug with android not sending cached message
Feature Request
[AGCORDOVA-4] - Use latest aerogear-android-push library (0.2)
[AGCORDOVA-5] - Use latest google-play-services
[AGCORDOVA-8] - Use Plugin android.support.v4 as dependency rather than adding the jar directly
[AGCORDOVA-9] - The example shipped with the plugin should use the latest API (simplification)
[AGCORDOVA-11] - Update the underlying iOS Push SDK
Automate plugin testing using grunt-cordova-plugin-jasmine.
10 years, 3 months