Failed to execute "atlas-run-standalone --product jira " - maven

I am new to atlassian-plugin-sdk, while running the command atlas-run-standalone --product jira, I am getting the following error
C:\Users\aaaaa>atlas-run-standalone --product jira
Executing: "D:\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" com.atlassia
n.maven.plugins:maven-amps-plugin:5.0.13:run-standalone -gs D:\atlassian-plugin-
sdk\apache-maven-3.2.1/conf/settings.xml -Dproduct=jira
[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder org.apache.maven.lifecycle.internal.builder.singlethrea
ded.SingleThreadedBuilder with a thread count of 1
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-amps-plugin:5.0.13:run-standalone (default-cli) # standalone-pom ---
Downloading: https://maven.atlassian.com/repository/public/com/atlassian/plugins
/rest/atlassian-rest-common/2.9.2-m01/atlassian-rest-common-2.9.2-m01.pom
Downloading: https://maven.atlassian.com/repository/public/com/sun/jersey/contri
bs/wadl-resourcedoc-doclet/1.8-atlassian-8/wadl-resourcedoc-doclet-1.8-atlassian
-8.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.018 s
[INFO] Finished at: 2015-02-20T10:27:34+05:30
[INFO] Final Memory: 9M/23M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-plugin:5.0.13:run-standalone (default-cli) on project standalone-pom:
Execution default-cli of goal com.atlassian.maven.plugins:maven-amps-plugin:5.0.13:run-standalone failed: Plugin com.atlassian.maven.plugins:maven-amps-plugin:5.0.13
or one of itsdependencies could not be resolved: Failed to collect dependencies at com.atlassian.maven.plugins:maven-amps-plugin:jar:5.0.13 ->
com.atlassian.plugins.rest:atlassian-rest-doclet:jar:2.9.2 -> com.atlassian.jersey:atlassian-jersey-restdoc:jar:1.0.3 ->
com.atlassian.plugins.rest:atlassian-rest-common:jar:2.9.2-m01: Failed to read artifact descriptor for com.atlassian.plugins.rest:atlassian-rest-common:jar:2.9.2-m01:
Could not transfer artifact com.atlassian.plugins.rest:atlassian-rest-common:pom:2.9.2-m01 from/to atlassian-public (https://maven.atlassian.com/repository/public):
sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unableto find valid certification path to requested target -> [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 rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResoluti
onException
C:\Users\aaaa>atlas-version
ATLAS Version: 5.0.13
ATLAS Home: D:\atlassian-plugin-sdk
ATLAS Scripts: D:\atlassian-plugin-sdk\bin
ATLAS Maven Home: D:\atlassian-plugin-sdk\apache-maven-3.2.1
--------
Executing: "D:\atlassian-plugin-sdk\apache-maven-3.2.1\bin\mvn.bat" --version -g
s D:\atlassian-plugin-sdk\apache-maven-3.2.1/conf/settings.xml
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T23:07:5
2+05:30)
Maven home: D:\atlassian-plugin-sdk\apache-maven-3.2.1
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_65\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"
Please help me in solving this issue
Note: I have changed my proxy setting in setting.xml in maven, but its of no use,
I am getting the same error again and again

I guess I replied to your question on answers.atlassian.com and here the answer will be the same: https://maven.atlassian.com is not trusted by your Java.
Here is what you need to make ti trusted:
Download the certificate manually
This depends on what browser you are using. For IE7, you need to browse to the website (eg. https://maven.atlassian.com) then:
Right click on the page and access its Properties menu
Click on the Certificates button
Click on the Details Tab
Choose Copy to File
You will be taken to the Certificate Export Wizard, click next
Choose a format of the certificate that you would like to choose then
save the certificate to a directory of your choice.
Install the certificate to your keystore
You can use Java's keytool command to import it to your keystore, for example:
keytool -import -file myCertificate.cer -keystore myKeystor
Source: https://confluence.atlassian.com/display/CONFKB/Unable+to+Install+Plugin+Due+to+Maven+SSL

Related

maven install jasper report error 308: Permanent Redirect [duplicate]

This question already has answers here:
JasperReports Maven broken?
(6 answers)
Dependency error in jasper-reports from itext
(13 answers)
Gradle Build Failure for JasperReports: Dependency Issue
(1 answer)
Closed 1 year ago.
I try install dependencies of my maven project but when I use "mvn install" I get this error for jasper report:
[INFO] Scanning for projects...
[INFO]
[INFO] --------------< com.projectSecret >--------------
[INFO] Building projectSecret
[INFO] --------------------------------[ war ]---------------------------------
Downloading from jaspersoft-third-party: http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/com/lowagie/itext/2.1.7.js5/itext-2.1.7.js5.pom
Downloading from jaspersoft-third-party: http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/org/olap4j/olap4j/0.9.7.309-JS-3/olap4j-0.9.7.309-JS-3.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.373 s
[INFO] Finished at: 2021-06-10T20:20:08-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project projectSecret: Could not resolve dependencies for project com.projectSecret.org:projectSecret:war:0.0.1-SNAPSHOT: Failed to collect dependencies at net.sf.jasperreports:jasperreports:jar:6.4.0 -> com.lowagie:itext:jar:2.1.7.js5: Failed to read artifact descriptor for com.lowagie:itext:jar:2.1.7.js5: Could not transfer artifact com.lowagie:itext:pom:2.1.7.js5 from/to jaspersoft-third-party (http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/): Transfer failed for http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/com/lowagie/itext/2.1.7.js5/itext-2.1.7.js5.pom 308 Permanent Redirect -> [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
any idea why this error or solution? Thanks!
I use Linux Mint 20 and :
Apache Maven 3.6.3
Maven home: /usr/share/maven
Java version: 1.8.0_292, vendor: Private Build, runtime: /usr/lib/jvm/java-8-openjdk-amd64/jre
OS name: "linux", version: "5.4.0-74-generic", arch: "amd64", family: "unix"
my pom.xml
I just ran into the same problem. It seams that iText is not availabel on public repos. Here https://github.com/TIBCOSoftware/jasperreports/issues/148 the solution is to add the following repo:
<repository>
<id>jaspersoft-third-party</id>
<url>https://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/</url>
</repository>
Edit: I need to change the url from http to https.

what is the cause of this openliberty docker error

Just following Product documentation instructions:
Please see Error log message.
Not sure what the error is and how to fix it.
mvn liberty:devc
[INFO] Scanning for projects...
[INFO]
[INFO] ------------< io.openliberty.guides:guide-getting-started >-------------
[INFO] Building guide-getting-started 1.0-SNAPSHOT
[INFO] --------------------------------[ war ]---------------------------------
[INFO]
[INFO] --- liberty-maven-plugin:3.3.4:devc (default-cli) # guide-getting-started ---
[INFO] CWWKM2102I: Using artifact based assembly archive : io.openliberty:openliberty- kernel:null:21.0.0.3:zip.
[INFO] CWWKM2102I: Using installDirectory : /home/zahid/Liberty-eclipse/guide-getting-started/start/target/liberty/wlp.
[INFO] CWWKM2102I: Using serverName : defaultServer.
[INFO] CWWKM2102I: Using serverDirectory : /home/zahid/Liberty-eclipse/guide-getting-started/start/target/liberty/wlp/usr/servers/defaultServer.
[INFO] Running maven-compiler-plugin:compile
[INFO] Copying 1 file to /home/zahid/Liberty-eclipse/guide-getting-started/start/target/liberty/wlp/usr/servers/defaultServer
[INFO] CWWKM2144I: Update server configuration file server.xml from /home/zahid/Liberty-eclipse/guide-getting-started/start/src/main/liberty/config/server.xml.
[INFO] Building Docker image...
[INFO] docker build --pull -f /tmp/tempDockerfile17415566016391532686 -t guide-getting-started-dev-mode /home/zahid/Liberty-eclipse/guide-getting-started/start
[ERROR] unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /tmp/tempDockerfile17415566016391532686: no such file or directory
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.343 s
[INFO] Finished at: 2021-03-20T16:28:39Z
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal io.openliberty.tools:liberty-maven-plugin:3.3.4:devc (default-cli) on project guide-getting-started: Could not build Docker image using Dockerfile: /home/zahid/Liberty-eclipse/guide-getting-started/start/Dockerfile. Address the following docker build error and then start dev mode again: unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /tmp/tempDockerfile17415566016391532686: no such file or directory RC=1 -> [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
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat
Resolution: Remove the snappy version from Ubuntu 20.04
$ sudo snap remove docker
then install using these instructions
https://docs.docker.com/engine/install/ubuntu/#uninstall-docker-engine
Problem: Snappy installation of docker was broken.

GitLab Runner No Compiler

need some help to help to solve this issue.
Iam running my gitlab ci, to test my maven project, everthing ist working fine but when its starting to compiling/building/installing following error recieves:
Running with gitlab-runner 10.5.0 (80b03db9)
on RolfsRunner 7d39f8f7
Using Shell executor...
Running on ISC-PRAKTIKANT...
Fetching changes...
Removing target/
HEAD is now at a7189518 7.2
Checking out a7189518 as rolf...
Skipping Git submodules setup
Checking cache for default...
Successfully extracted cache
$ cd C:\Program Files\GitLab-Runner\builds\7d39f8f7\0\dev\imsPlatform & mvn compile
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for de.immersight:imsPlatform:war:1.0
[WARNING] 'dependencies.dependency.systemPath' for immersight:imsLibrary:jar should use a variable instead of a hard-coded path C:\Users\Rolf\Desktop\imsLibrary-1.0.jar # line 59, column 19
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ---------------------< de.immersight:imsPlatform >----------------------
[INFO] Building imsPlatform 1.0
[INFO] --------------------------------[ war ]---------------------------------
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) # imsPlatform ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Program Files\GitLab-Runner\builds\7d39f8f7\0\dev\imsPlatform\de\immersight\stats\database\versions
[INFO] Copying 1 resource
[INFO] Copying 154 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) # imsPlatform ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 172 source files to C:\Program Files\GitLab-Runner\builds\7d39f8f7\0\dev\imsPlatform\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.769 s
[INFO] Finished at: 2018-03-13T13:05:58+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project imsPlatform: Compilation failure
[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?
[ERROR]
[ERROR] -> [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/MojoFailureException
Running after script...
$ echo CI_ENVIRONMENT_NAME
CI_ENVIRONMENT_NAME
ERROR: Job failed: exit status 1
My eclipse and windows cmd compiling fine without problems everthing is installed and all environment variables are set:
C:\Users\Rolf>mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
Maven home: C:\Users\Rolf\Maven-3.5.3\bin\..
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_161\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
C:\Users\Rolf>javac -version
javac 1.8.0_161
I had the same problem. After installing a JDK and editing the environment variables I had to restart my gitlab-runner with administrator privileges.
gitlab-runner.exe restart
May not interesting for you anymore ;)

Maven 3.5 build error

I have installed maven latest version 3.5 ,iam trying to build a fuse project and getting below error and warning.
output of mvn -version in command prompt:
C:\Temp\Fuse6.3>mvn -version
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T20:39:06+01:00)
Maven home: C:\Temp\fuse 6.3\apache-maven-3.5.0\bin\..
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: C:\Temp\fuse 6.3\java\jdk1.8.0_151\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Can you please help.
[INFO] ------------------------------------------------------------------------
[WARNING] Could not transfer metadata com.company.esb.fuse:core:0.0.1-SNAPSHOT/maven-metadata.xml from/to redhat-ga-repository (https://maven.repository.redhat.com/ga): Cannot access https://maven.repository.redhat.com/ga with type default using the available connector factories: BasicRepositoryConnect
orFactory
[WARNING] Could not transfer metadata com.company.esb.fuse:core:0.0.1-SNAPSHOT/maven-metadata.xml from/to jboss-earlyaccess-repositor (http://maven.repository.redhat.com/earlyaccess/all/): Cannot access http://maven.repository.redhat.com/earlyaccess/all/ with type default using the available connector
factories: BasicRepositoryConnectorFactory
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2.260 s
[INFO] Finished at: 2017-10-23T10:58:29+01:00
[INFO] Final Memory: 10M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project core: Could not resolve dependencies for project com.company.esb.fuse:core:jar:0.0.1-SNAPSHOT: Failed to collect dependencies at com.company.esb.fuse:core:jar:0.0.1-SNAPSHOT -> org.apache.camel:camel-core:jar:2.17.0.redhat-630262: Failed to read artifact descripto
r for org.apache.camel:camel-core:jar:2.17.0.redhat-630262: Could not transfer artifact org.apache.camel:camel-core:pom:2.17.0.redhat-630262 from/to redhat-ga-repository (https://maven.repository.redhat.com/ga): Cannot access https://maven.repository.redhat.com/ga with type default using the availab
le connector factories: BasicRepositoryConnectorFactory: No transporter factories registered -> [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 in Atlassian SDK

I am currently trying to get started with the Atlassian SDK and I've installed it as it is described in the Atlassian SDK Documentation. But when I'm running a SDK-command, it doesn't work. For example, when I run the command
atlas-run-standalone --product jira
it fails with the following output:
Executing: "C:\Users\XXX\Programme\apache-maven-3.1.1\bin\mvn" com.atlassian.maven.plugins:maven-am
ps-plugin:4.2.20:run-standalone -gs C:\Users\XXX\atlassian-plugin-sdk\apache-maven/conf/settings.xm
l -Dproduct=jira
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Maven Stub Project (No POM) 1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-amps-plugin:4.2.20:run-standalone (default-cli) # standalone-pom ---
[INFO] Google Analytics Tracking is enabled to collect AMPS usage statistics.
[INFO] Although no personal information is sent, you may disable tracking by adding <allowGoogleTracking>false
</allowGoogleTracking> to the amps plugin configuration in your pom.xml
[INFO] Sending event to Google Analytics: AMPS:jira - Run Standalone
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.861s
[INFO] Finished at: Thu Apr 24 09:32:47 CEST 2014
[INFO] Final Memory: 16M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.atlassian.maven.plugins:maven-amps-plugin:4.2.20:run-standalone (
default-cli) on project standalone-pom: Execution default-cli of goal com.atlassian.maven.plugins:ma
ven-amps-plugin:4.2.20:run-standalone failed: An API incompatibility was encountered while executing
com.atlassian.maven.plugins:maven-amps-plugin:4.2.20:run-standalone: java.lang.NoSuchMethodError: o
rg.apache.maven.execution.MavenSession.getRepositorySession()Lorg/sonatype/aether/RepositorySystemSe
ssion;
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>com.atlassian.maven.plugins:maven-amps-plugin:4.2.20
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/C:/Users/XXX/.m2/repository/com/atlassian/maven/plugins/maven-amps-plugin/4
.2.20/maven-amps-plugin-4.2.20.jar
[ERROR] urls[1] = file:/C:/Users/XXX/.m2/repository/com/atlassian/core/atlassian-core/4.0/atlassian
-core-4.0.jar
# more [ERROR] urls[x] = ...
[ERROR] urls[130] = file:/C:/Users/XXX/.m2/repository/org/twdata/maven/mojo-executor/1.5.1/mojo-exe
cutor-1.5.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] -> [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 arti
cles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
Some further information to my machine:
Windows 7 Professional, x64
javac 1.7.0_45
JAVA_HOME is set, %JAVA_HOME%/bin has been added to PATH
And the information responded by the atlas-version command:
ATLAS Version: 4.2.20
ATLAS Home: C:\Users\XXX\atlassian-plugin-sdk
ATLAS Scripts: C:\Users\XXX\atlassian-plugin-sdk\bin
ATLAS Maven Home: C:\Users\XXX\atlassian-plugin-sdk\apache-maven
--------
Executing: "C:\Users\XXX\Programme\apache-maven-3.1.1\bin\mvn" --versi
n-plugin-sdk\apache-maven/conf/settings.xml
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-1
Maven home: C:\Users\XXX\Programme\apache-maven-3.1.1
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_45\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Have you set ATLAS_MVN to use your own installation of Maven? The Atlassian SDK doesn't support Maven 3.1+ in the 4.x releases due to an incompatible change in Maven itself (MNG-5354).
There is a fix (AMPS-1029); until upgrading, use Maven 3.0 or the mvn that's bundled with AMPS.
AMPS 5.0 has now been released (AMPS SDK 5.0.0 Release Notes) with that fix included, and support for Maven 3.1.

Resources