Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-10611

In Spring Boot, search pattern of resource auto deployment is too lax

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • spring-boot 3.2.4, spring-boot 3.0.4, spring-boot 3.1.4, spring-boot 3.3.2
    • spring-boot
    • None

      Steps to reproduce

      1. Start a simple Spring Boot application with absent @EnableProcessApplication annotation
        • This triggers auto deployment
      2. Observe the console output

      Observed behavior
      I can see the following warnings:

      2019-07-12 13:03:25.106  WARN 72661 --- [           main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:/Users/tasso/.m2/repository/org/camunda/bpm/dmn/camunda-engine-dmn/7.12.0-alpha1-ee/camunda-engine-dmn-7.12.0-alpha1-ee.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource
2019-07-12 13:03:25.107  WARN 72661 --- [           main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:/Users/tasso/.m2/repository/org/camunda/bpm/dmn/camunda-engine-feel-api/7.12.0-alpha1-ee/camunda-engine-feel-api-7.12.0-alpha1-ee.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource
2019-07-12 13:03:25.107  WARN 72661 --- [           main] s.b.s.c.i.DefaultDeploymentConfiguration : unable to determine if resource URL [jar:file:/Users/tasso/.m2/repository/org/camunda/bpm/dmn/camunda-engine-feel-juel/7.12.0-alpha1-ee/camunda-engine-feel-juel-7.12.0-alpha1-ee.jar!/META-INF/maven/org.camunda.bpm.dmn/] is a deployable resource

      Problem
      The search pattern to discover resources takes folders with .dmn/ suffix into account

      Expected behavior
      Search pattern takes only files into account

        This is the controller panel for Smart Panels app

            [CAM-10611] In Spring Boot, search pattern of resource auto deployment is too lax

            Thorben Lindhauer added a comment -

            We are closing this ticket as part of our backlog grooming. Reasons:

            • We did not receive sufficient evidence that this ticket is important

            Thorben Lindhauer added a comment - We are closing this ticket as part of our backlog grooming. Reasons: We did not receive sufficient evidence that this ticket is important

              Unassigned Unassigned
              tassilo.weidner Tassilo Weidner
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: