Grails
  1. Grails
  2. GRAILS-4388

problems with managing application.properties in source control systems such as perforce

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1
    • Fix Version/s: 2.3-M1
    • Component/s: Configuration
    • Labels:
      None
    • Environment:
      Any system using check-out source control system such as "perforce" and continous build system

      Description

      application.properties is required to be checked in. With a source control system such as perforce, this file becomes "read-only" and needs to be checked out to be modified.
      Running various grails commands such as "grails Bootstrap" fail if this file is read-only.

      There appears to be no simple workaround for such source-control systems. Source control systems such as SVN don't have this immediate problem, but do have the pain point that the file appears to be modified when it need not be.

      Example error:

      [exec] Compilation error: Error persisting metadata to file [/some-path/SomeApp/application.properties]: /some-path/SomeApp/application.properties (Permission denied)

        Activity

        Hide
        Niko Schmuck added a comment -

        Note that also the taglib descriptor files (web-app/WEB-INF/tld) have to be checked out (writeable) to allow grails (1.1.x) to be successfully launched.
        Therefore I think GRAILS-4246 "Application does not start if taglibs are read-only" is related to this issue.

        Show
        Niko Schmuck added a comment - Note that also the taglib descriptor files (web-app/WEB-INF/tld) have to be checked out (writeable) to allow grails (1.1.x) to be successfully launched. Therefore I think GRAILS-4246 "Application does not start if taglibs are read-only" is related to this issue.
        Hide
        hamish cunningham added a comment -

        the SVN problem could be ameliorated if the grails sorted the properties list before writing to applications.properties?

        Show
        hamish cunningham added a comment - the SVN problem could be ameliorated if the grails sorted the properties list before writing to applications.properties?
        Hide
        Tim Miller added a comment -

        This one and GRAILS-4246 were both reported in the context of problems in the developer environment but perhaps more critically it seems like an operational issue to me - applications are deployed into the production environment read-only (or at least not writeable by the hosting process). Is there really a need for self-modifying code?

        Show
        Tim Miller added a comment - This one and GRAILS-4246 were both reported in the context of problems in the developer environment but perhaps more critically it seems like an operational issue to me - applications are deployed into the production environment read-only (or at least not writeable by the hosting process). Is there really a need for self-modifying code?
        Hide
        Jeff Scott Brown added a comment -

        Tim,

        I don't understand your concern. Which files are being modified in your production environment?

        Show
        Jeff Scott Brown added a comment - Tim, I don't understand your concern. Which files are being modified in your production environment?
        Hide
        Graeme Rocher added a comment -

        This should no longer be relevant in 2.3 as we don't modify application.properties

        Show
        Graeme Rocher added a comment - This should no longer be relevant in 2.3 as we don't modify application.properties

          People

          • Assignee:
            Unassigned
            Reporter:
            Jamie Hunter
          • Votes:
            5 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Last Reviewed:

              Development