[jira] [Created] (ARIES-785) Blog tests can pass when blog sample is broken

["Holly Cummins (Created) (JIRA)" <ji...@apache.org>]

Blog tests can pass when blog sample is broken
----------------------------------------------

                 Key: ARIES-785
                 URL: https://issues.apache.org/jira/browse/ARIES-785
             Project: Aries
          Issue Type: Bug
          Components: Samples
    Affects Versions: 0.4
            Reporter: Holly Cummins
            Priority: Minor


https://issues.apache.org/jira/browse/ARIES-784 fixed a problem with the version numbers used to generate the config.ini (set in the samples pom.xml). Most of the bundles in the blog assembly don't start, which means the blog sample completely doesn't work, but the blog tests still pass. This means the blog tests aren't really validating the blog sample.

It looks like the blog assembly is using version numbers set as explicit properties in the samples pom.xml:

   <!-- External Dependencies -->
        <cmVersion>3.2.0-v20070116</cmVersion>
        <servicesVersion>3.1.200-v20070605</servicesVersion>
        <asmVersion>3.2</asmVersion>
        <paxLoggingApiVersion>1.4.0</paxLoggingApiVersion>
        <paxLoggingServiceVersion>1.4.0</paxLoggingServiceVersion>

whereas the version used in the dependencies.properties for the itests comes from parent/default-parent/pom.xml:

            <dependency>
                <groupId>org.ops4j.pax.logging</groupId>
                <artifactId>pax-logging-api</artifactId>
                <version>1.5.0</version>
            </dependency>

Hardcoding the version in two places seems to make the versions going out of synch inevitable.
 




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira