On Tuesday, February 3, 2015, Corinne Krych <corinnekrych@gmail.com> wrote:

The iea behind submodules was to group all demo from a central repos. aerogear-ios-cookbook is doing the same. I initially borrow the idea from Luke :P
Some submodules can not be moved to cookbook like PushQuickstart

hrm, not sure :-) Perhaps we should move that. I will create a ticket to trsck this

 

so I’d go for solution 2

++
Corinne

> On 03 Feb 2015, at 20:10, Bruno Oliveira <bruno@abstractj.org> wrote:
>
> Good morning, I'm struggling to understand why we have submodules here:
> https://github.com/aerogear/aerogear-backend-cookbook. Do we have a good
> reason for it?
>
> To give you some context, I already tagged the cookbook backend as 0.0.1
> ("stable") and would like to generate the binaries from this tag.
>
> To be it doesn't make any sense on having submodules there and we have 2
> alternatives:
>
> 1. Move the repositories to the aerogear-backend-cookbook
> 2. Remove the submodules
>
> Thoughts?
>
> --
>
> abstractj
> PGP: 0x84DC9914
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
Sent from Gmail Mobile

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev