Re: [sca-assembly] Fwd: Runtime-specific artifacts in conformance tests

[Mike Edwards <mike_edwards@uk.ibm.com>]

Jim,

These files are all part of the Tuscany-specific
client.


Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com

From:	Jim Marino <jim.marino@gmail.com>
To:	OASIS Assembly <sca-assembly@lists.oasis-open.org>
Date:	13/12/2009 16:31
Subject:	[sca-assembly] Fwd: Runtime-specific artifacts in conformance tests

---

I also missed several other files:

- log4j.properties
- commons-logging.properties
- openjpa.xml

Jim


Begin forwarded message:

From: Jim Marino <jim.marino@gmail.com>
Date: December 13, 2009 3:57:31 PM
GMT+01:00
To: OASIS Assembly <sca-assembly@lists.oasis-open.org>
Subject: Runtime-specific artifacts in
conformance tests

In looking at the conformance assembly tests, I noticed
a number of runtime-specific artifacts required for the build. Given these
are supposed to be vendor-neutral, they probably should be removed before
the tests are finalized:

- Tuscany SCA API jar
- Tuscany Maven Zip plugin
- Tuscany Maven Bundle Plugin
- Tuscany Maven Eclipse Plugin
- Tuscany runtime and Eclipse runtime libraries transitively pulled in
by the Test_Client module. Running the Maven dependency plugin shows:

org.oasis-open.sca.assembly:Test_Client:jar:1.0
[INFO] +- org.apache.tuscany.sca:tuscany-sca-api:jar:2.0-SNAPSHOT:compile
[INFO] +- org.apache.tuscany.sca:tuscany-node-launcher-equinox:jar:2.0-SNAPSHOT:compile
[INFO] |  +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] |  +- org.eclipse:osgi:jar:3.5.0-v20090520:compile
[INFO] |  \- commons-cli:commons-cli:jar:1.2:compile
[INFO] +- org.apache.tuscany.sca:tuscany-node-api:jar:2.0-SNAPSHOT:compile

I realize the Tuscany SCA API jar was included because the OASIS version
is not available from a public Maven repository. However, this could be
handled by including the OASIS jar in the subversion repository and creating
a Maven project that invokes an Ant script to install the jar in the local
Maven repository where it will be available to the build. If would helpful,
I can provide this.

I am unclear as to why the other plugins and runtime-specific artifacts
are needed to build the test artifacts. I'm happy to help remove these
once someone explains what they are intended for.

Jim

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU