Its being put into the cookbook.
On Thu 01 Aug 2013 01:47:03 AM EDT, Matthias Wessendorf wrote:
On Tue, Jul 30, 2013 at 9:52 AM, Matthias Wessendorf
<matzew(a)apache.org <mailto:matzew@apache.org>> wrote:
On Mon, Jul 29, 2013 at 4:24 PM, Summers Pittman
<supittma(a)redhat.com <mailto:supittma@redhat.com>> wrote:
In the meeting this morning and in the JIRA we discussed
moving the
PusheeDemo code into the cookbook application.
Arguments for:
Push code is now in the main repo.
Push demo joins other demo code
Arguments against:
Push demo is no longer stand alone
Will need to document the push demo code is in the cookbook
Thoughts?
Since the PusheeDemo is also used for the tutorial (see [1]), it
should be standalone or at least it should be not too complex to
get up and running,
when interested in our GCM bits
However, if the cookbook is easy to setup and not 5 or more
unrelated steps (==> to 'push' unrelated steps) are required for
running the thing, I am fine
in moving this to the cookbook project.
Any comments ?
-Matthias
[1]
https://issues.jboss.org/browse/AGPUSH-21
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org <mailto:aerogear-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev