We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The VS Code extension runs a command like this to generate a new java project:
mvn archetype:generate -DarchetypeGroupId='com.microsoft.azure' -DarchetypeArtifactId='azure-functions-archetype' -DgroupId='com.function' -DartifactId='javart1' -Dversion='1.0-SNAPSHOT' -Dpackage='com.function' -DappName='myappname1' -B
In the past, it would set this in the new pom.xml:
<functionAppName>myappname1</functionAppName>
But now it's ignoring the appName parameter and always doing a name like this:
appName
<functionAppName>javart1-20200227165500266</functionAppName>
Should the VS Code extension stop prompting for appName? I don't have a preference, but the README here seems to imply the parameter is still supported: https://github.com/microsoft/azure-maven-archetypes/tree/develop/azure-functions-archetype#azure-parameters
@Flanker32 @andxu Seems like this PR is what changed it: #128
The text was updated successfully, but these errors were encountered:
@Flanker32 Let's enable those parameters to unblock automation use case of the archetype
Sorry, something went wrong.
@EricJizbaMSFT Really sorry for the late reply, we have added the parameters back in the latest archetype release, here is the release note
No branches or pull requests
The VS Code extension runs a command like this to generate a new java project:
In the past, it would set this in the new pom.xml:
But now it's ignoring the
appName
parameter and always doing a name like this:Should the VS Code extension stop prompting for appName? I don't have a preference, but the README here seems to imply the parameter is still supported: https://github.com/microsoft/azure-maven-archetypes/tree/develop/azure-functions-archetype#azure-parameters
@Flanker32 @andxu Seems like this PR is what changed it: #128
The text was updated successfully, but these errors were encountered: