Uploaded image for project: 'Kuali Rice Development'
  1. Kuali Rice Development
  2. KULRICE-1824

Discontinue use of the META-INF directory for configuration files

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: Not version specific
    • Component/s: Development
    • Labels:
      None

      Description

      I think I started this convention with the original plugin layout using META-INF/workflow.xml (regretfully so). That directory has special meaning within Java and so I think we should stop using it for configuration files and go back and fix the places where we do use it.

      We could allow it to be used still for plugins moving forward to support backward compatibility if desired but I think it should at the very least be deprecated there.

        Attachments

          Activity

          Hide
          natjohns Nate Johnson (Inactive) added a comment -

          Are you just saying for the workflow.xml file? I think this is the default for all non-java resources according to maven.

          Show
          natjohns Nate Johnson (Inactive) added a comment - Are you just saying for the workflow.xml file? I think this is the default for all non-java resources according to maven.
          Hide
          ewestfal Eric Westfall added a comment -

          Maven wants all non-java resources in META-INF by default? I wasn't aware of that. I was thinking more along the lines of all of the configuration files we have that we put in that directory.

          Show
          ewestfal Eric Westfall added a comment - Maven wants all non-java resources in META-INF by default? I wasn't aware of that. I was thinking more along the lines of all of the configuration files we have that we put in that directory.
          Hide
          natjohns Nate Johnson (Inactive) added a comment -

          Maybe maven just assume the resources directory, not resources/META-INF... I can't remember right off hand. Were you also thinking of removing the resources directory, or just META-INF where there are no specs?

          Show
          natjohns Nate Johnson (Inactive) added a comment - Maybe maven just assume the resources directory, not resources/META-INF... I can't remember right off hand. Were you also thinking of removing the resources directory, or just META-INF where there are no specs?
          Hide
          ewestfal Eric Westfall added a comment -

          Maven assumes that resources are under <module-name>/src/main/resources so I think we want to keep that but I don't think it prescribes any meaning to the META-INF directory.

          Show
          ewestfal Eric Westfall added a comment - Maven assumes that resources are under <module-name>/src/main/resources so I think we want to keep that but I don't think it prescribes any meaning to the META-INF directory.
          Hide
          natjohns Nate Johnson (Inactive) added a comment -

          That works for me.

          Show
          natjohns Nate Johnson (Inactive) added a comment - That works for me.
          Hide
          jcoltrin Jessica Coltrin (Inactive) added a comment -

          no longer an issue.

          Show
          jcoltrin Jessica Coltrin (Inactive) added a comment - no longer an issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              ewestfal Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours
                2h
                Remaining:
                Remaining Estimate - 2 hours
                2h
                Logged:
                Time Spent - Not Specified
                Not Specified