Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-895

Arquillian config-impl-base is not a part of spock-standalone

    XMLWordPrintable

    Details

      Description

      Cloned from Core, but Spock has similar problem. Not adding config-impl-base means no Extension configuration in standalone mode.

      When configuration was split, the arquillian-config-impl-base was made a dependency of container only

      ./container/spi/pom.xml:            <artifactId>arquillian-config-impl-base</artifactId> <!-- ILLEGAL DEPENDENCY, fix with new Config module -->
      ./container/impl-base/pom.xml:            <artifactId>arquillian-config-impl-base</artifactId> <!-- ILEGAL DEPENDENCY, resolved with new Config API -->
      ./bom/pom.xml:                <artifactId>arquillian-config-impl-base</artifactId>
      ./config/impl-base/pom.xml:    <artifactId>arquillian-config-impl-base</artifactId>
      

      This means that when no container is on classpath, e.g. standalone mode of junit/testng, ArquillianDescriptor is not created at all.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  aslak Aslak Knutsen
                  Reporter:
                  kpiwko Karel Piwko
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: