I agree about those benefits (even if they are weak) but I'd like to have the
drawbacks measured better.
Doing an easy things does not mean it has no implications, see when we decided
to remove the specialpurpose from R13
Jacques
Le 21/01/2015 02:32, Ron Wheeler a écrit :
It will make the project look more professional which has some benefit in reviews by IT departments of potential adopters or by technical reviewers
for blogs or journals.
I am not sure if this can be quantified but it is a benefit.
The cost seems pretty low since it should only affect the build and the docs.
Ron
On 20/01/2015 8:13 PM, Adrian Crum wrote:
I disagree. This is an open source software project where decisions should be made based on good design principles. The work is being done by
volunteers, so I don't see how "cost/benefit" applies.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 1/20/2015 5:04 PM, Hans Bakker wrote:
Jacopo,
'nice' is not enough reason to change the directory structure.....
Please this is a business application where decisions should be taken
based on cost/benefit.
Regards, Hans
On 20/01/15 18:41, Jacopo Cappellato wrote:
In my opinion it would be nice to review how we organize the code in
our components and switch to a directory layout that is more inline
with what other projects are doing, for example:
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
More specifically I would like to switch from, for example:
script/org/ofbiz/product/
src/org/ofbiz/product/
src/org/ofbiz/product/test/
to:
src/main/java/org/ofbiz/product/
src/main/minilang/org/ofbiz/product/
src/main/groovy/...
src/test/java/org/ofbiz/product/
What do you think?
Jacopo
