Having director structure like:
|-- src
| |--main
| | `--java
| | `-- //rest of the code
| |--test
| `--java
| `-- org
| `-- ofbiz
| `-- securityext
| |-- AuthorizationTests.java
| `-- DaTest2.groovy
Will also confirm to Maven directory structure and it will make Maven
build system integration easier if needed some time in future.
Thanks,
Raj
On Wednesday 18 May 2011 11:03 AM, Adrian Crum wrote:
I prefer the original proposal. I don't like having two different
source code folders.
Keep in mind that we informally agreed that there will be disruptions
post 11.x branch. I believe this one will be one of many worthwhile
changes.
-Adrian
On 5/17/2011 10:25 PM, David E Jones wrote:
To avoid disrupting the current directory structure, it would be
better to avoid:
move: component/src -> component/src/main/java
result: component/src/main/java, component/src/text/java
and instead not move component/src at all and have:
component/src
component/test-src
... or something along those lines.
-David
On May 17, 2011, at 10:12 PM, Ganath Rathnayaka wrote:
Hi devs,
According to my project I suggested some changes to be done to
separate the
test classes from the code itself. Please let me know your ideas
about the
suggested structure.
Also I came up with the structure for module securityext. Can I
separate the
code as follows? Please let me know your ideas.
current structure
.
|-- src
| `-- org
| `-- ofbiz
| `-- securityext
| |-- test
| | |-- AuthorizationTests.java
| `-- DaTest2.groovy
after test/code separation
.
|-- src
| |--main
| | `--java
| | `-- //rest of the code
| |--test
| `--java
| `-- org
| `-- ofbiz
| `-- securityext
| |-- AuthorizationTests.java
| `-- DaTest2.groovy
--
thanks
Ganath
