[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]