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

Environment configuration is overridden by arquillian.xml

        Details

        • Workaround Description:
          Hide

          Remove affected properties from arquillian.xml descriptor

          Show
          Remove affected properties from arquillian.xml descriptor

          Description

          It is not possible to define JAVA_HOME and JBOSS_HOME for managed containers via system properties because these values are used only during configuration creation and they will be overridden by arquillian.xml value.

          This is not desired behaviour how to make test execution flexible enough.

            Gliffy Diagrams

              Issue Links

              is incorporated by

              Enhancement - An enhancement or refactoring of existing functionality ARQ-921 Make environment variables available for property replacement in configuration

              • Major - A request that should be considered seriously but is not a show stopper.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                alrubinger Andrew Rubinger added a comment -

                Pushed Karel's quick fix into "next":

                https://github.com/arquillian/arquillian/commit/e8de51aaff3195665892dfa9798e5c03b68aa9ae

                Needed to get us moving forward.

                Show
                alrubinger Andrew Rubinger added a comment - Pushed Karel's quick fix into "next": https://github.com/arquillian/arquillian/commit/e8de51aaff3195665892dfa9798e5c03b68aa9ae Needed to get us moving forward.
                Hide
                Permalink
                kpiwko Karel Piwko added a comment -

                ARQ-148 implementation allows user to set any property via reasonable default. However, this does not work for environment variables but for properties only.

                Suppose following:

                <configuration>
                		 
                   ...
                		 
                   <property name="foo" value="${foo:bar}"/>
                		 
                   <property name="env_foo" value "${ENV_FOO:bor}" />
                		 
                </configuration>

                If a System property foovalue is defined (via Surefire plugin properties <foo>value</foo>), it will make foo to have value "value", if not it will be bar.
                However, if ENV_FOO environment variable is defined, it has no effect, since Arquillian interpolates system properties only.

                Show
                kpiwko Karel Piwko added a comment - ARQ-148 implementation allows user to set any property via reasonable default. However, this does not work for environment variables but for properties only. Suppose following: < configuration > ... < property name = "foo" value = "${foo:bar}" /> < property name = "env_foo" value "${ENV_FOO:bor}" /> </ configuration > If a System property foovalue is defined (via Surefire plugin properties <foo>value</foo>), it will make foo to have value "value", if not it will be bar. However, if ENV_FOO environment variable is defined, it has no effect, since Arquillian interpolates system properties only.
                Hide
                Permalink
                aslak Aslak Knutsen added a comment -

                fixed by ARQ-921

                Show
                aslak Aslak Knutsen added a comment - fixed by ARQ-921

                  People

                  • Assignee:
                    kpiwko Karel Piwko
                    Reporter:
                    kpiwko Karel Piwko
                  • Votes:
                    3 Vote for this issue
                    Watchers:
                    4 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Development