Note that there are some explanatory texts on larger screens.

plurals
  1. POSudden compilation error during maven release
    primarykey
    data
    text
    <p>I have recently started having trouble releasing a maven project which has worked fine for a long time now. The project consists of several modules with a structure looking something like:</p> <pre><code>project_server project_webserver project_qp project_qp_ingr project_repo project_repo_ingr </code></pre> <p>Both modules project_qp and project_repo are dependent on project_webserver with ${project.version} references.</p> <p>The project is build using Jenkins and everything works fine when I am building snapshot builds. When I try to build a release with version 3.1-RC1 in a maven release build configuration with the options/goals "-Dresume=false release:prepare release:perform -e", everything works fine in the "clean, verify" phase, but in the "deploy, site-deploy", project_repo suddenly doesn't compile. </p> <p>The compilation errors consist of the module not finding classes from the project_webserver module. However, the project_qp_ingr module has already been built and is working fine.</p> <p>All of this suggests to me that there is something wrong with the reference from project_repo_ingr to project_webserver but since the project builds fine when I am building snapshot releases.</p> <p>The pom of project_repo_ingr looks like:</p> <pre><code>&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"&gt; &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;artifactId&gt;project_repo_ingr&lt;/artifactId&gt; &lt;name&gt;project_repo_ingr&lt;/name&gt; &lt;packaging&gt;jar&lt;/packaging&gt; &lt;parent&gt; &lt;groupId&gt;com.apptus.ecom&lt;/groupId&gt; &lt;artifactId&gt;project_repo&lt;/artifactId&gt; &lt;version&gt;3.1.0-SNAPSHOT&lt;/version&gt; &lt;/parent&gt; &lt;dependencies&gt; &lt;dependency&gt; &lt;groupId&gt;com.apptus.ecom&lt;/groupId&gt; &lt;artifactId&gt;project_webserver&lt;/artifactId&gt; &lt;version&gt;${project.version}&lt;/version&gt; &lt;/dependency&gt; &lt;!-- Test dependencies --&gt; &lt;dependency&gt; &lt;groupId&gt;com.apptus.ecom&lt;/groupId&gt; &lt;artifactId&gt;project_webserver&lt;/artifactId&gt; &lt;version&gt;${project.version}&lt;/version&gt; &lt;type&gt;test-jar&lt;/type&gt; &lt;scope&gt;test&lt;/scope&gt; &lt;/dependency&gt; &lt;/dependencies&gt; &lt;/project&gt; </code></pre> <p>I have omitted some dependencies but that is pretty much it. Both the module project_repo_ingr and project_qp_ingr have the dependency to both the regular artifact and the test-jar.</p> <p>I use Java 6, Maven 2 and Jenkins 1.436 with M2 Release Plugin 0.8.1.</p> <p>Any help is greatly appreciated, I have torn my hair all day long about this.</p> <p>Update: The changes that I have made since the last time this worked is branching the svn repo from the trunk to a release branch. The jenkins job in trunk has been copied into one for the branch and the svn path is changed. I have also updated the part of the project_server pom.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload