Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-8769

(7.0.z) Location of configuration files for standalone mode

    XMLWordPrintable

Details

    • Clarification
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • None
    • Compatibility/Configuration

    Description

      While backporting configuration files from WildFly/EAP 7.1 we have found that EAP 7.1 is overriding some configuration files for standalone mode from wildfly-core. Namely standalone.conf, standalone.conf.bat and standalone.conf.ps1.

      In EAP 7.1 is the situation following:

      • EAP 7.1 is consuming public wildfly-core
      • specific configuration files are stored in private repo of EAP 7.1. These files are overriding default wildfly-core files

      In EAP 7.0:

      • EAP 7.0 is consuming private wildfly-core-eap
      • currently there are no EAP specific files

      The question is, when we want to take EAP specific files from 7.1 where we should backport them in 7.0. In private wildfly-core-eap or directly in EAP?

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8240 [GSS](7.0.z) Unable to disable the automatic GC log flags specifically in the standalone.sh/.bat

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is related to

          Clarification - A clarification needed to a specification based on community feedback JBEAP-8770 (7.1.x) Location of EAP specific files after moving wildfly-core to private repo

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rstancel@redhat.com Radovan Stancel
              rstancel@redhat.com Radovan Stancel
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: