Hi, Mike.
The code structure of OASIS conformance tests only partially follows the
maven conventions and that makes it difficult to build in maven or load the
code into Eclipse. There are two basic issues:
1) Mixing the java and resource files in the same folder. Maven uses filters
to exclude resource files from source/testSource folders and exclude java
files from the resource/testResource folders.
2) Nesting java files under the src/main/resources. For example,
General_Java contains java files.
At this point, Tuscany uses an ANT script to reorganize the code after it is
checked out from SVN. Would it be possible to improve the structure to be
something like the following?
The java files are placed under src/test/java/<TestName>:
src/test/java/Tests:
src/test/java/General_Java:
We can either set up the testSource to include individual java folders as
test sources or use different package names (?) to distinguish the tests
(?).
The resource files are placed under src/test/resources/<TestName>:
src/test/resources/ASM_4003:
src/test/resources/ASM_4004:
src/test/resources/General_Java:
Thanks,
Raymond
--------------------------------------------------
From: "Mike Edwards" <[email protected]>
Sent: Wednesday, July 29, 2009 7:53 AM
To: <[email protected]>
Subject: Re: running the otests
ant elder wrote:
Should we delete the fixed_version branch of the otest now that the
current one is being used and fixed_version is quite back level? It
slows down checkouts and updates keeping it there and we can add a new
fixed version back if we need to later. I'll delete it in a day or two
if no one wants to keep it.
...ant
+1
Mike
