The new Repo is now here !!

I'll create some JIRA's to update the Readme, update, remove the code from the main repo, etc...

Question.  Will this require a major version bump once i remove the code?  i'm thinking yes

On Mon, Aug 31, 2015 at 5:11 AM, Corinne Krych <> wrote:
This way, we're getting closer to native libs approach with separate libs

On 31 August 2015 at 10:55, Lukáš Fryč <> wrote:
You are right Luke, this start to make more and more sense :-)

On Mon, Aug 24, 2015 at 7:22 PM, Luke Holmquist <> wrote:
so i decided to take a gander at the push client lib in the aerogear.js project.   Currently if someone would like to use it,  they have a couple options.

1. download the whole lib,
2. download a custom build from the website
3. download a custom build from bower
4. create a custom build from source

In the past i think i was against breaking out pieces of the JS lib into separate repo's since we could just use the AeroGearComponents repo i created for custom builds.  But i think with the state of the JS lib(not sure where it's going), it might make sense to, at least with the push lib(perhaps the simplePush polyfill also) to break those out into separate repo's similar to the other client projects.

I think the starting vision of the project has changed, so perhaps this change is good.(this should probably be a whole separate thread)

Now that Chrome and Safari have push in the browser, FF is getting it also very soon,  it's possible this part of the library will be used more



aerogear-dev mailing list

aerogear-dev mailing list

aerogear-dev mailing list