http://dev.clojure.org/jira This file is an XML representation of an issue en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJ-681 Clojure <p>See <a href="http://dev.clojure.org/display/design/Common+Contrib+Build">Common Contrib Build</a> wiki page and the lengthy <a href="http://groups.google.com/group/clojure-dev/browse_thread/thread/8d11cdd6d27ceb13">clojure-dev discussion</a></p> <p>For examples of the CI/release process under Hudson, see <a href="http://build.clojure.org/job/clojure-testbuild/">clojure-testbuild</a></p> CLJ-681

Build Clojure with Maven 2

Enhancement Major Closed Completed Stuart Sierra Stuart Sierra Fri, 26 Nov 2010 14:05:33 -0600 Fri, 1 Mar 2013 12:47:02 -0600 Wed, 5 Jan 2011 07:20:08 -0600 Backlog Release 1.3 0 1 <p>Replaces previous patch.</p> <ul> <li>fixed SCM URLs in pom.xml</li> </ul> <p>Maven is capable of using the directory structure we already have. It seems this patch is doing two things: getting us onto maven, and reorganizing the project. Is there any reason these can't be considered separately?</p> <p>Updated patch replaces previous patches.</p> <p>This does minimal file/directory renaming while preserving the same functionality as the previous patches.</p> <p>But an older problem has resurfaced: the nondeterministic load-order sometimes causes compilation to fail. For example, <a href="http://build.clojure.org/job/clojure-testbuild/22/console">on Hudson</a></p> <p>Patch maven-build-4.diff.gz replaces previous patches.</p> <p>This works around compilation-order issues by using a bootstrap script to compile namespaces in the correct order.</p> <p>Patch maven-build-5.diff.gz replaces previous patches.</p> <p>This fixes a few more testing issues.</p> <p>Finally got a <a href="http://build.clojure.org/job/clojure-testbuild/32/">successful staging release</a></p> <p>Unfortunately, the JAR file is misnamed. This is a <a href="http://groups.google.com/group/clojure-maven-plugin/browse_thread/thread/16b5c73adb7a672c">clojure-maven-plugin bug</a> that will be fixed in the next release.</p> <p>Patch maven-build-6.diff.gz replaces previous patches.</p> <p>This updates to clojure-maven-plugin version 1.3.7; README updates.</p> <p>Patch maven-build-7.diff.gz replaces previous patches.</p> <p>This patch adds back in a simplified build.xml for local development using Ant only.</p> <p>The Ant build.xml script reads the project version number from pom.xml, so pom.xml remains the definitive project description.</p> <p>Patch maven-build-8.diff.gz replaces previous patches.</p> <p>This version uses a hybrid Maven + Ant build process. For local development, only Ant is needed. The POM does not depend on anything outside of the standard Maven toolchain and the Sonatype open-source deployment configuration.</p> <p>Patch "maven-build-8" answers those questions by postponing them.</p> <p>This patch is ready to test and apply.</p> <p>To elaborate: patch "maven-build-8" avoids both clojure-maven-plugin and bootstrap load order by using maven-ant-plugin and Ant to drive the Clojure steps in the build.</p> <p>We still need to address these issues, but that may take a long time, and we want to move forward with releases to public repositories.</p> <p>Can you please run down two small issues:</p> <p>(1) I get a warning on the maven build:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java">[WARNING] [WARNING] Some problems were encountered <span class="code-keyword">while</span> building the effective model <span class="code-keyword">for</span> org.clojure:clojure:jar:1.3.0-testbuild10-SNAPSHOT [WARNING] 'build.plugins.plugin.version' <span class="code-keyword">for</span> org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 52, column 15 [WARNING] 'build.plugins.plugin.version' <span class="code-keyword">for</span> org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 181, column 15 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For <span class="code-keyword">this</span> reason, <span class="code-keyword">future</span> Maven versions might no longer support building such malformed projects. [WARNING]</pre> </div></div> <p>(2) The version is set to 1.3.0-testbuild10-SNAPSHOT. Am I supposed to change this by hand-editing the pom?</p> <p>Patch maven-build-9.diff.gz replaces previous patches.</p> <p>Differences from previous patches:</p> <ul> <li>Adds plugin coordinates to fix the warnings reported by Stu Halloway</li> <li>Avoids compiling the test sources twice</li> <li>Correctly sets POM version to 1.3.0-master-SNAPSHOT</li> </ul> <p>Reported issues should be fixed, although I cannot reproduce the warning messages.</p> <p>What version of Maven produced those warnings?</p> <p>Patch 10 merely updates patch 9 to apply to current master. (A test namespace had changed. The list of test files has always been hard-coded and fragile, but that's a patch for another day.)</p> <p>I tested all the Ant and Maven commands documented in the reademe, and everything looks sensible.</p> <p>Patch 10 is bad. The pom file from patch 9 was lost, and my local environment didn't notice somehow. Will test and resubmit a patch 11 that is basically patch 10 with the correct pom.xml from patch 9. </p> <p>Grumble.</p> <p>Patch 11 is basically patch 10 + the correct pom.xml from patch 9. </p> Approval Ok Global Rank Patch Code and Test Waiting On stu