Karaf
  1. Karaf
  2. KARAF-1122

Feature <configfile/> creates an empty file if the file URL is not resolved

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.4
    • Fix Version/s: 2.2.6, 3.0.0
    • Component/s: karaf-feature
    • Labels:
      None

      Issue Links

        Activity

        Hide
        Jean-Baptiste Onofré added a comment -

        Fixed on karaf-2.2.x: revision 1222359.

        Show
        Jean-Baptiste Onofré added a comment - Fixed on karaf-2.2.x: revision 1222359.
        Hide
        Jean-Baptiste Onofré added a comment -

        Fixed on trunk: revision 1222353.

        Show
        Jean-Baptiste Onofré added a comment - Fixed on trunk: revision 1222353.
        Hide
        Jean-Baptiste Onofré added a comment -

        In a feature, when we use something like:

        <configfile finalname="etc/my.xml">
        mvn:groupId/artifactId/version/xml
        </configfile>

        if the mvn URL could not resolved (the URLConnection stream is null), the finalname is created empty.

        It could be painful as the file already exists and if the connection is back, the file is not overwritten.

        Show
        Jean-Baptiste Onofré added a comment - In a feature, when we use something like: <configfile finalname="etc/my.xml"> mvn:groupId/artifactId/version/xml </configfile> if the mvn URL could not resolved (the URLConnection stream is null), the finalname is created empty. It could be painful as the file already exists and if the connection is back, the file is not overwritten.

          People

          • Assignee:
            Jean-Baptiste Onofré
            Reporter:
            Jean-Baptiste Onofré
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development