quarkusio/quarkus · error · BuildException
Please config the <appName> in pom.xml.
Error message
Please config the <appName> in pom.xml.
What it means
Before deploying, validateParameters checks that an Azure function app name was provided. If the appName string is blank, the command throws BuildException with the constant EMPTY_APP_NAME ('Please config the <appName> in pom.xml.'). The app name is mandatory to create/locate the Azure Functions app.
Source
Thrown at extensions/azure-functions/deployment/src/main/java/io/quarkus/azure/functions/deployment/AzureFunctionsDeployCommand.java:168
public String getType() {
return "Quarkus";
}
@Override
public AzureString getDescription() {
return AzureString.fromString("Quarkus");
}
};
OperationThreadContext ctx = OperationThreadContext.current();
push.invoke(ctx, dummy);
} catch (Exception e) {
}
}
protected void validateParameters(AzureFunctionsConfig config, String appName) throws BuildException {
// app name
if (StringUtils.isBlank(appName)) {
throw new BuildException(EMPTY_APP_NAME);
}
if (appName.startsWith("-") || !appName.matches(APP_NAME_PATTERN)) {
throw new BuildException(format(INVALID_APP_NAME, appName));
}
// resource group
if (StringUtils.isBlank(config.resourceGroup())) {
throw new BuildException(EMPTY_RESOURCE_GROUP);
}
if (config.resourceGroup().endsWith(".") || !config.resourceGroup().matches(RESOURCE_GROUP_PATTERN)) {
throw new BuildException(INVALID_RESOURCE_GROUP_NAME);
}
// asp name & resource group
if (StringUtils.isNotEmpty(config.appServicePlanName())
&& !config.appServicePlanName().matches(APP_SERVICE_PLAN_NAME_PATTERN)) {
throw new BuildException(format(INVALID_SERVICE_PLAN_NAME, APP_SERVICE_PLAN_NAME_PATTERN));
}
if (config.appServicePlanResourceGroup().isPresent()
&& StringUtils.isNotEmpty(config.appServicePlanResourceGroup().orElse(null))View on GitHub (pinned to e1c734241f)
Solutions
- Add <appName>your-function-app-name</appName> to the azure-functions Maven plugin configuration in pom.xml
- Or pass -DappName=your-function-app-name to the Maven command
- Verify the pom you edited is the module where quarkus:deploy runs
Example fix
<!-- before --> <configuration> <resourceGroup>my-rg</resourceGroup> </configuration> <!-- after --> <configuration> <appName>my-quarkus-func</appName> <resourceGroup>my-rg</resourceGroup> </configuration>
Defensive patterns
Strategy: validation
Validate before calling
if (appName == null || appName.isBlank()) {
throw new IllegalArgumentException("<appName> must be configured before quarkus:deploy");
} Prevention
- Add appName (and resourceGroup) to the plugin configuration at project creation time
- Fail fast in CI if -DappName is absent for deploy jobs
- Keep a single source of truth (pom properties) for deployment names
When it happens
Trigger: Running quarkus:deploy without <appName> in the plugin configuration and without -DappName=... on the command line.
Common situations: New project scaffolded but deployment properties never filled in; property defined in the wrong pom (module without the plugin); CI passes no -DappName override.
Related errors
- Path must be set if using file auth config
- Please config the <resourceGroup> in pom.xml.
- Auth config file not found: ${path}
- Auth config file does not define type: ${path}
- Failed to parse removed resource '${entry.key}=${entry.resou
AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05).
Data as JSON: /api/errors/13eef35ceec43438.
Report an issue: GitHub.