sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-assembly] Conformance tests rely on vendor-specific version of theOASIS Java APIs
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: OASIS Assembly <sca-assembly@lists.oasis-open.org>
- Date: Tue, 12 Jan 2010 09:31:01 +0000
Logged as: http://www.osoa.org/jira/browse/ASSEMBLY-210
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:
| 11/01/2010 18:17
|
Subject:
| [sca-assembly] Conformance tests rely
on vendor-specific version of the OASIS Java APIs |
TARGET: SCA Assembly Conformance Tests
DESCRIPTION:
The current conformance tests rely on a Tuscany jar containing
Tuscany's version of the OASIS spec APIs. The conformance tests should
by default use a sanctioned OASIS jar. Besides being more appropriate,
the dependence on Tuscany jars also introduces a practical issue of
how to upgrade the conformance tests when breaking API changes are
introduced. As it currently stands, in order to introduce non-
compatible API changes in the conformance tests, Tuscany must first
update their version of the API jar. Given that the Tuscany runtime
likely compiles against the runtime API jar, this probably means the
conformance tests cannot be updated with API changes until the Tuscany
runtime can first compile against them.
SVN Version: 426
PROPOSAL:
There are several simple solutions to the problem that do not require
OASIS publishing a Maven artifact for the spec APIs, although that is
probably the best long-term solution:
1. Include a version of the spec APIs in the conformance test build as
a separate Maven module
2. Include a precompiled version of the spec API jar in the
conformance test SVN repo and create a Maven module that calls out to
an Ant script to install the jar in the local Maven repository on the
test runner machine
3. Include a Maven module that calls out to an Ant script to download
the OASIS jar from an OASIS URL and stall the jar in the local Maven
repository on the test runner machine
I can provide implementations of #2 and #3 if desired.
---------------------------------------------------------------------
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]