Broccoli #498

Closed
MajorBreakfast opened this Issue Feb 16, 2014 · 9 comments

Projects

None yet

6 participants

@MajorBreakfast
Contributor

@joliss's broccoli has now beta status. The ultimate plan is for it being used by ember-cli and EAK disappears. I propose having it in parallel to grunt in EAK for the meantime.

@stefanpenner and others: Yes, no, maybe?

Why? Because EAK is practically the ultimate test environment.

@joliss
Collaborator
joliss commented Feb 16, 2014

Hm, I personally don't want to invest more time in EAK.

@Pradeek
Contributor
Pradeek commented Feb 17, 2014

If we are not upgrading EAK, is there some work being done on Ember CLI at the moment? I see very little activity there. If we can outline a plan for Ember CLI + Broccoli, I'm ready to pitch in as soon as possible.

@stefanpenner
Owner

@Pradeek we are working hard on this, even as i type this.

(me and @joefiorini)

@Pradeek
Contributor
Pradeek commented Feb 17, 2014

@stefanpenner Anyway I can help? Or try it out?

@joefiorini
Contributor

@Pradeek Please feel free to clone and try it on any existing EAK apps you have. ember build and ember server should work with the existing grunt workflow. The first run of the broccoli integration is inbound in the next few days. If you could report any problems you run into, that would be a huge help. Thanks!

@Pradeek
Contributor
Pradeek commented Feb 17, 2014

Awesome. Will let you guys know.

@medokin
medokin commented Feb 17, 2014

I've read that Windows is not yet supported. I hope the switch will only take place if this will change.

@stefanpenner
Owner

@medokin yes.

Expect the transition to be gradual.

Once we have a beta, we will hopefully get some early adopters, which will result in bugs reports and many fixes. Even without windows support at the start, this should allow us to iterate. Then as time permits (and before the final release) windows support will be added.

@MajorBreakfast I am slightly unsure if we should add support to both projects, as the CLI should easily replace the functionality in EAK. I wouldn't be apposed to this, I wont have the bandwidth to maintain both, but welcome PR's and experiments.

@MajorBreakfast
Contributor

Okay was a nice idea but I now think that building it in both places isn't the way to go. EAK will be replaced anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment