[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on project standalone-pom: Failed to deploy artifacts: Could not transfer artifact org.kobil.keycloak:keycloak:jar:9.0.0 from/to (https://pkgs.dev.azure.com//_packaging/k/maven/v1): Transfer failed for https://pkgs.dev.azure.com//_packaging/k/maven/v1/org/kobil/keycloak/keycloak-core/9.0.0/keycloak-9.0.0.jar 401 Unauthorized -> [Help 1]
After creating a feed with project scope, (Project with public visibility) able to download the published package without PersonalAccessToken.
Related
The following build commands failed:
PhaseScriptExecution [CP]\ Embed\ Pods\ Frameworks /Users/runner/Library/Developer/Xcode/DerivedData/abc-clsnlxjxhbvxthhdyflygxcirhow/Build/Intermediates.noindex/abc.build/Release-iphoneos/abc.build/Script-44A1C33C9FB70F4680C11CB7.sh (in target 'abc' from project 'abc')
(1 failure)
I need to create .IPA file by Azure Pipeline
I'm trying to build a Bot for MS Teams using TeamsFX extension for Visual Studio. I've started from the demo and so far (not without excruciating pain) managed to get my functionality implemented.
Now I want to deploy my Bot to AWS (not Azure) so I want to build the Bot Package with its manifest but when I choose "Build Teams Package" I get the following error:
[2021-08-18T17:59:50.918Z] [Info] - [core] start task:executeUserTask, inputs:{"projectPath":"/Users/teamsapp","platform":"vsc","vscodeEnv":"local","function-dotnet-checker-enabled":{}}
[2021-08-18T17:59:50.920Z] [Debug] - [core] success to aquire lock on: /Users/teamsapp/.fx
[2021-08-18T17:59:50.986Z] [Debug] - [core] success to get questions for executeUserTask
[2021-08-18T17:59:50.987Z] [Error] - [Teams Toolkit] Teams Package build failed!
[2021-08-18T17:59:51.043Z] [Debug] - [core] persist project setting file: /Users/teamsapp/.fx/settings.json
[2021-08-18T17:59:51.044Z] [Debug] - [core] lock released on /Users/teamsapp/.fx
[2021-08-18T17:59:51.044Z] [Info] - [core] finish task:executeUserTask
[2021-08-18T17:59:51.044Z] [Error] - code:AppStudioPlugin.TeamsPackageBuildError, message: Teams package build failed. You must run 'Provision in the Cloud' first to fill out certain fields in manifest.
How can I build the teams app package?
We tried it using TeamsFX and it worked fine for us. Could you please check if all the fields in manifest are Updated? I hope you are following all the required points as mentioned in Create a Microsoft Teams app package.
I'm trying to run an Azure DevOps pipeline for talend ESB project but I got this error message:
[ERROR] Failed to execute goal on project routines: Could not resolve dependencies for project org.example.local_project.code:routines:jar:7.3.1: Could not find artifact org.talend.libraries:crypto-utils:jar:5.2.0 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn <args> -rf :routines
Any help please.
According to the error message log, this error generally occurs when Maven could not download dependencies. Possible causes for this error are:
The POM misses the declaration of the which hosts the
artifact.
The repository you have configured requires authentication and Maven
failed to provide the correct credentials to the server. In this
case, make sure your ${user.home}/.m2/settings.xml contains a
declaration whose matches the of the remote
repository to use. See the Maven Settings Reference for more
details.
The remote repository in question uses SSL and the JVM running Maven
does not trust the certificate of the server.
There is a general network problem that prevents Maven from
accessing any remote repository, e.g. a missing proxy configuration.
You have configured Maven to perform strict checksum validation and
the files to download got corrupted.
Maven failed to save the files to your local repository, see
LocalRepositoryNotAccessibleException for more details.
You can refer to this document to troubleshoot.
I am getting the following error on mvn azure-webapp:deploy
[ERROR] Failed to execute goal com.microsoft.azure:azure-webapp-maven-plugin:1.9.1:deploy (default-cli) on project mprsreporting: Status code 403 -> [Help 1]
I am following the instructions here...
This was an issue with multiple subscriptions and the maven plug in attempting to deploy on a wrong subscription. Fixed it by changing the default subscription
I want to generate microservices application with only Back-end code.
I found solution in this.
And I used jhipster --skip-client but It's still have some Font-end files like node-modules,packege.json...
After that, I found another solution instead of jhipster --skip-client . I use jhipster:server and it works . I didn't have any Font-End file,but I could run by use mvnw . This is my error
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10.184 s
[INFO] Finished at: 2019-05-08T16:20:28+07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.codehaus.mojo:properties-maven-plugin:1.0.0:read-project-properties (default) on project test-mic: Properties could not be loaded from File: C:\Users\DatNT80\Desktop\TestMic\sonar-project.properties -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
How can I resolve my problem
jhipster --skip-client is the correct way to generate a server only application. By invoking jhipster server, you are using an internal "jhipster sub-generator" which will likely result in an incomplete or even non working application.
The package.json and node_modules are not frontend files. They are required to locally install jhipster as a JavaScript dependency of your project (jhipster is coded in JS). This way when invoking jhipster in your app directory, it is garanteed to use the same jhipster version as the one your app was generated with.