Harbs, sorry that you are frustrated. But any change we'll do to refactor things, will have the same effect in your application code base: You'll need to adapt you code to the changes. That was that always people do when this kind of changes comes.
If you want to go back, that means we'll freeze in the past and all discussion in the end will make the same effect. Right now, Maven build is green in all parts (frameworks, projects, themes, examples....), so I think is more easy for all of us to go forward, and simply fix you Application. Why don't you want to help on this? Why the best way is revert a project framework to solve an application case? Simply don't understand that way of proceed and seems very hard with the work done for others to make this project better. 2018-05-10 10:34 GMT+02:00 Harbs <harbs.li...@gmail.com>: > Let me just say that I’m *very* frustrated right now. > > I’m busy chasing down all kinds of odd issues caused by a refactoring that > we didn’t agree on. > > I really don’t have the time to be doing so right now… :-( > > Carlos, you REALLY should have: > a) properly discussed this all *before* you made these changes. > b) done this on a feature branch. > > At this point, I’d like to just revert all the refactoring changes. > > Harbs > > > On May 10, 2018, at 9:08 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com> > wrote: > > > > In that point I'm feeling that Even if couple of PMC members or > committers > > have some resistance, changes are being done no matter what. > > -- Carlos Rovira http://about.me/carlosrovira
