OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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



Jim,

Thanks for taking this careful look at the OASIS Assembly test artifacts.

First, to comment on the various build artifacts.

The build artifacts are only provided as an example and are not strictly part of the testcase suite.
They are provided as a convenience and as a guide to how the test suite can be built.  No-one is
obliged to use any of them.  We cannot presume that people using the test suite will be happy to
use Maven or indeed any other build system - but the materials that are there are Maven based
and do work.

The 3 plugins that you identify are publicly available Maven plugins that assist in some common
tasks relating to building with Maven.  Again, no-one is obliged to use them.


The Tuscany SCA API JAR is as you rightly observe a necessary evil at the moment.  Ideally, there
would be an OASIS version of the SCA API jar publicly available from a Maven repository.  I would
appreciate your assistance in making this a reality, in which case this Tuscany dependency would
go away.  (I suspect that the Tuscany file would go away as well - the Tuscany project has no
interest in maintaining this file).


Regarding the dependencies of the Test_Client module, what you are seeing are the dependencies
of the test client as built as a client to the Tuscany runtime (I noted that the build artifacts are examples
and the client example assumes that it is a Tuscany client).

I am happy to work with you on creating a binary package that can be a client to the Fabric3 runtime.
I have not separated out the client into a "Tuscany client binary", "Fabric3 client binary" etc since
until this point no-one had come forward with anything other than a Tuscany client.  It will be good to
have a second client and a second SCA runtime and I am happy to work with you to make this a reality.


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 15:01
Subject: [sca-assembly] 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


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php









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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]