Hi Adam,
I'm not talking about how to do it but to answer the question : is the
community want to do it ?
Is the community want to maintain only a framework and not an ERP ?
Split the project in several part.
Maven could be a solution, but before choosing a solution, we must be
sure that it is a common decision.
Then we can define action plan on how to do it and go ahead :)
Julien.
Le 07/05/2015 16:19, Adam Heath a écrit :
On 05/07/2015 05:48 AM, Julien NICOLAS wrote:
I see a lot of debate about adding new functionality that allow to
improve development, compile, manage sources, merge with another
framework, but the debate on the division of project extensions seems
not to interest. It seems to me extremely important to facilitate
development and therefore, ultimately, the visibility of the project
in the developers community.
You don't understand the force behind my work then. That's the goal,
to be able to require only just what we(Brainfood) need for a
deployment. For reference, we don't write our frontends in any of the
widget systems.
The built-in build system, the use of svn, are holding the project
back. It's not just about switching because of switching, but the new
tools open the door for everything you are talking about.
So, please be patient.
