I am trying to setup a pipeline that does the following command:
# This is a sample build configuration for Java (Maven).# Check our guides at https://confluence.atlassian.com/x/zd-5Mw for more examples.# Only use spaces to indent your .yml configuration.# -----# You can specify a custom docker image from Docker Hub as your build environment.image: maven:3.6.1
pipelines: default: - step: caches: - maven script: # Modify the commands below to build your repository. #- mvn -B verify # -B batch mode makes Maven less verbose - mvn clean package deploy -DmuleDeploy
It gets done downloading dependencies then I get the following error:
<span>Downloaded from : <a href="https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0/plexus-utils-3.0.jar" target="_blank" rel="noopener nofollow noreferrer">https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-utils/3.0/plexus-utils-3.0.jar</a> (226 kB at 17 MB/s)</span><span>[INFO] </span><span>[INFO] --- mule-maven-plugin:3.2.7:clean (default-clean) @ javatestflow ---</span><span>[INFO] </span><span>[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ javatestflow ---</span><span>[INFO] </span><span>[INFO] --- mule-maven-plugin:3.2.7:validate (default-validate) @ javatestflow ---</span><span>[INFO] </span><span>[INFO] --- mule-maven-plugin:3.2.7:initialize (default-initialize) @ javatestflow ---</span><span>[INFO] </span><span>[INFO] --- mule-maven-plugin:3.2.7:generate-sources (default-generate-sources) @ javatestflow ---</span><span>[INFO] </span><span>[INFO] --- mule-maven-plugin:3.2.7:process-sources (default-process-sources) @ javatestflow ---</span><span>[INFO] About to fetch required dependencies for artifact: com.mycompany:javatestflow:pom:1.0.0-SNAPSHOT. This may take a while...</span><span>[INFO] ------------------------------------------------------------------------</span><span>[INFO] BUILD FAILURE</span><span>[INFO] ------------------------------------------------------------------------</span><span>[INFO] Total time: 31.060 s</span><span>[INFO] Finished at: 2019-07-05T17:22:25Z</span><span>[INFO] ------------------------------------------------------------------------</span><span>[ERROR] Failed to execute goal org.mule.tools.maven:mule-maven-plugin:3.2.7:process-sources (default-process-sources) on project javatestflow: There was an exception while creating the repository of [MavenProject: com.mycompany:javatestflow:1.0.0-SNAPSHOT @ /opt/atlassian/pipelines/agent/build/pom.xml]: There was an issue resolving the dependency tree for the artifact [/opt/atlassian/pipelines/agent/build/pom.xml]: Failed to collect dependencies at com.mycompany:javatestflow:pom:1.0.0-SNAPSHOT -> com.mulesoft.connectors:mule-salesforce-connector:jar:mule-plugin:9.6.0 -> <a href="http://com.sun.xml.ws/" target="_blank" rel="noopener nofollow noreferrer">com.sun.xml.ws</a>:jaxws-rt:jar:2.2.10: Failed to read artifact descriptor for <a href="http://com.sun.xml.ws/" target="_blank" rel="noopener nofollow noreferrer">com.sun.xml.ws</a>:jaxws-rt:jar:2.2.10: 1 problem was encountered while building the effective model for <a href="http://com.sun.xml.ws/" target="_blank" rel="noopener nofollow noreferrer">com.sun.xml.ws</a>:jaxws-rt:2.2.10</span><span>[ERROR] [ERROR] 'dependencyManagement.dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${tools.jar} @</span><span>[ERROR] -> [Help 1]</span><span>[ERROR] </span><span>[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.</span><span>[ERROR] Re-run Maven using the -X switch to enable full debug logging.</span><span>[ERROR] </span><span>[ERROR] For more information about the errors and possible solutions, please read the following articles:</span><span>[ERROR] [Help 1] <a href="http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException" target="_blank" rel="noopener nofollow noreferrer">http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException</a></span>
<span>My project has those variables at a level to where I can't really change them or hard code a value in them. Has anyone found a way around this? Sorry, new to the Docker/Pipelines scene. </span>
<span>I can run this all locally with maven. I haven't had a chance to figure out completely how to run the pipeline stuff locally to continue to troubleshoot</span>