Posted by
David E. Jones-2 on
URL: http://ofbiz.116.s1.nabble.com/GSoC-Project-update-Code-and-Test-separation-of-Ofbiz-and-Implementing-pure-webdriver-tp3660318p3669433.html
I've been doing a little more research on Maven, and I'm guessing that the pattern that Ganath is proposing is at least partly based on the convention for src directories in Maven (which appears to be required for use of Maven, BTW... ie with their convention over configuration approach, which is certainly nice for various reasons even if it does impose certain constraints).
If we wanted our src directories to be Maven-friendly, it would look like:
<component>/src/main/java
<component>/src/test/java
In other words, if we're going to make a change, perhaps we should change to that as the Maven conventions seem to be turning into industry standards (perhaps because the Maven conventions are some of the few that exist and are even remotely widely used).
Along that vein, we might also consider moving the files under <component>/script and even <component>/config to:
<component>/src/main/resources
BTW, just as a side note if we ever had Maven POM files, their location in each component would just be <component>/pom.xml
-David
On Jul 13, 2011, at 11:09 PM, Ganath Rathnayaka wrote:
> Hi David,
> Since we have the current structure of the code,
> component/src/main
> component/src/test
> which contains separated test and code. We can do the code transformation
> to,
> component/src
> component/src-test
> easily. But to build the project, it may need some work to change the build,
> commons and macros xml files. Since I need to finish the project before 16th
> August, I and Erwan need to change the scope of the project if this change
> need to be done because we have another part (implementing a webdriver) of
> the project to be done.
> Here I am expecting all your final decision before I make my next movement.
>
> thanks
> Ganath