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


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

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

Subject: Implementing the Resolution to ASSEMBLY-210 - creating an accessibleversion of the SCA-J API & Annotation JAR file


We resolved the ASSEMBLY-210 issue some time ago - this had to do with the fact that until now, the SCA-J TC had not made available
a version of the JAR file of the APIs and Annotations in a form that is consumable by the SCA test suites - and that as a consequence, those
test suites have been using a version of the JAR file available from Apache Tuscany.

So, to action the resolution of the issue, I have done the following:

a) Created a version of the APIs and Annotations JAR file for SCA-J that is loaded into the OASIS SVN repository in a form that matches the
     requirements of the Maven build system (ie it is laid out in a form that matches that of a Maven repo).

b) Adjusted the (sample) Maven build files for the test suite artifacts to use the new JAR file - organized so that the build files will
     automatically find and download the JAR if it is not already present on the machine used to build and run the test suite.

The JAR file a) is found under:


...sca-caa-apis-1.1-CD04.jar  (as of 13/07/2010 )

This file is already built using the sample Maven build file for the SCA-J APIs and Annotations JAR.
To create the new layout needed for the repository format, a new section was added to this build file
which is activated by the command

      mvn deploy

...which places the JAR file into a structure on the disk on the machine where the command is run
The file can be committed from there to the SVN repository on Apache (it is expected that this will be
done very infrequently, only when a new CD of the Java CAA specification is published).

The sample pom.xml build files in the test suites (those that build Java artifacts) are then adjusted as follows:

use the JAR published in the OASIS SVN repository:

        <!-- This is the SCA API bundle: published by OASIS -->

...and in the root pom.xml file of each test suite, a reference to the OASIS SVN repository was added treating it like a Maven repository...

<!-- Material for the OASIS SVN repo -->
       <!-- End of material for OASIS SVN repo -->

With luck, this should make everyone happy - and we can declare on the SCA-J website that the JAR file is available in Maven format
from the SVN repo treated as a Maven repo...

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

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]