Azure functions core tools Stuck

I am trying to run the function locally..
With the command **mvn azure-functions:run**
while func gives me this
C:\Users\skasam>func

%%%%%%
%%%%%%
@ %%%%%% @
@@ %%%%%% @@
@@@ %%%%%%%%%%% @@@
@@ %%%%%%%%%% @@
@@ %%%% @@
@@ %%% @@
@@ %% @@
%%
%

Azure Functions Core Tools
Core Tools Version: 3.0.3477 Commit hash: 5fbb9a76fc00e4168f2cc90d6ff0afe5373afc6d (32-bit)
Function Runtime Version: 3.0.15584.0

Usage: func [context] [context] [-/--options]

Contexts:
azure Commands to log in to Azure and manage resources
durable Commands for working with Durable Functions
extensions Commands for installing extensions
function Commands for creating and running functions locally
host Commands for running the Functions host locally
kubernetes Commands for working with Kubernetes and Azure Functions
settings Commands for managing environment settings for the local Functions host
templates Commands for listing available function templates

Actions:
start Launches the functions runtime host
--port [-p] Local port to listen on. Default: 7071
--cors A comma separated list of CORS origins with no spaces. Example: https://functions.azure.com
,https://functions-staging.azure.com
--cors-credentials Allow cross-origin authenticated requests (i.e. cookies and the Authentication header)
--timeout [-t] Timeout for the functions host to start in seconds. Default: 20 seconds.
--useHttps Bind to https://localhost:{port} rather than http://localhost:{port}. By default it creates
and trusts a certificate.
--cert for use with --useHttps. The path to a pfx file that contains a private key
--password to use with --cert. Either the password, or a file that contains the password for the pfx f
ile
--language-worker Arguments to configure the language worker.
--no-build Do no build current project before running. For dotnet projects only. Default is set to fal
se.
--enableAuth Enable full authentication handling pipeline.
--functions A space seperated list of functions to load.
--verbose When false, hides system logs other than warnings and errors.
--dotnet-isolated-debug When specified, set to true, pauses the .NET Worker process until a debugger is attached.
--enable-json-output Signals to Core Tools and other components that JSON line output console logs, when applica
ble, should be emitted.
--json-output-file If provided, a path to the file that will be used to write the output when using --enable-j
son-output.

new Create a new function from a template. Aliases: new, create
--language [-l] Template programming language, such as C#, F#, JavaScript, etc.
--template [-t] Template name
--name [-n] Function name
--authlevel [-a] Authorization level is applicable to templates that use Http trigger, Allowed values: [function, a
nonymous, admin]. Authorization level is not enforced when running functions from core tools
--csx use old style csx dotnet functions

init Create a new Function App in the current folder. Initializes git repo.
--source-control Run git init. Default is false.
--worker-runtime Runtime framework for the functions. Options are: dotnet, dotnetIsolated, node, python, powe
rshell, custom
--force Force initializing
--docker Create a Dockerfile based on the selected worker runtime
--docker-only Adds a Dockerfile to an existing function app project. Will prompt for worker-runtime if not
specified or set in local.settings.json
--csx use csx dotnet functions
--language Initialize a language specific project. Currently supported when --worker-runtime set to nod
e. Options are - "typescript" and "javascript"
--managed-dependencies Installs managed dependencies. Currently, only the PowerShell worker runtime supports this f
unctionality.

logs Gets logs of Functions running on custom backends
--platform Hosting platform for the function app. Valid options: kubernetes
--name Function name

When I give this **mvn azure-functions:run**
it is stucking after
[INFO] Azure Function App's staging directory found at %function app location%

Reproduce the Java project locally with `mvn azure-functions:run` and Azure Functions Core Tools 3.0.3477. Start with the command output showing the staging directory and compare it with the `func` host startup behavior. Done means the local function run either completes or reports a clear actionable error instead of remaining stuck.

Written by the indexing model from the issue text.