Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-686

introduce an override flag to configfile element so that we get chance to not override the finalname if it already exist

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.1
    • Fix Version/s: 2.2.2, 3.0.0
    • Component/s: None
    • Labels:
      None

      Description

      currently http feature has configuration like
      <feature name="http" version="2.2.1" resolver="(obr)">
      <configfile finalname="/etc/jetty.xml">mvn:org.apache.karaf/apache-karaf/2.2.2-SNAPSHOT/xml/jettyconfig</configfile>
      <config name="org.ops4j.pax.web">
      org.osgi.service.http.port=8181
      javax.servlet.context.tempdir=${karaf.data}/pax-web-jsp
      org.ops4j.pax.web.config.file=${karaf.base}/etc/jetty.xml
      </config>
      This means each time we install http feature it will download jettyconfig.xml remotely and override the local etc/jetty.xml, so any configuration we saved in local etc/jetty.xml will lose.
      We should ship jetty.xml in kit etc folder and always refer it for the http feature, which is easier for customer to configure the jetty.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ffang Freeman Fang
                Reporter:
                ffang Freeman Fang
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: