Skip to content

Use deferred logging rather than System.out to report jars on the classpath with Class-Path manifest attributes that point to non-existent files when using DevTools #16883

Closed
@TurtleBeach

Description

@TurtleBeach

When I run a spring-boot application that depends on azure-spring-boot-starter (created by spring-initialzr), a message indicates various grpc jar files listed in the manifest for grpc-netty-shaded-1.14.0.jar do not exist. The manifest apparently expects all associated grpc jar files to be in the same folder as grpc-netty-shaded-1.14.0.jar (i.e., **…\io\grpc\grpc-netty-shaded\1.14.0**), yet in my local repository the associated jars each exist in separate folders under ...io/grpc (for example, the grpc-core jar is at …\io\grpc\grpc-core\1.14.0\grpc-core-1.14.0.jar).

The misconfiguration appears to have no impact on actually running the application, but it is disconcerting to see the message, and it is not clear under what circumstances things might break as I add more functionality to the application.
Jack

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions