Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<p>There appears to be a few efforts to get Scala to work with Maven, so I thought it would be useful to collect all the ideas here and see what code is currently available. Once that is done I would be happy to review any of the plugins and maybe we can collect them into one project, give everyone access who participated and make one decent toolchain for Scala.</p>

<p>If folks put their names here and where there implementations are I'll review the code and make some suggestions for improvements and what might be merged. Probably wouldn't be too hard to make something decent quickly.
<br class="atl-forced-newline" />
<br class="atl-forced-newline" /></p>

<p>In listing the separate projects below can you put each under a major heading. I'd like to see how many different projects that distinct sets of people are working on i.e. are we looking 2, 5, or 7 different projects going on simultaneously. I don't want to miss anything when I start looking at all the code.</p>

<p>The issues I want to look at solving are:</p>
<ul>
	<li>Combine the best parts of all the different Scala bits for Maven and help fix anything in Plexus or Maven itself that might be blocking good integration.</li>
	<li>A standard Scala packaging that will correspond to an optimized Scala lifecycle in Maven. This should allow a very terse definition of Scala project</li>
	<li>An optimized execution of the scala lifecycle in m2eclipse</li>
</ul>

<h3>Issues Seen by the Community</h3>

<ol>
	<li>Scala currently does not support backwards binary compatibility across release numbers. This has led to some issues with scala libraries either requiring users to always stay &quot;current&quot; or put tools on top of maven to release multiple &quot;versions&quot; each of which is compatible with a single Scala version.  Currently the approach is to include the Scala version first in the project's version, e.g. &quot;2.7.3-1.0-SNAPSHOT&quot; would mean your lirbary is at version 1.0-SNAPSHOT using scala 2.7.3.   It would be ideal if either scala become more backwards compatible or there were some way to manage this sanely inside maven.</li>
	<li>The maven-eclipse-plugin is unaware of either the pom configuration (source directories mostly) from the maven-scala-plugin, nor the eclipse metadata needed for the Scala Development Tools.  It would be ideal if there was some integration point we could work towards to ensure compliance and reduce surprise for users.</li>
</ol>

<h3>Maven And Scala Community</h3>

<ul>
	<li><a href="http://groups.google.com/group/maven-and-scala">The Google Group</a></li>
	<li><a href="http://code.google.com/p/esmi/wiki/ScalaMavenSupportTaskList">The Current Goal/Task List</a></li>
	<li>Repository : <a href="http://scala-tools.org">scala-tools.org</a></li>
</ul>

<h4>Maven And Scala Community Related Projects</h4>

<h5>maven-scala-plugin</h5>

<ul>
	<li>Status - production</li>
	<li>Goals
	<ul>
		<li>Integrate the Scala compiler into the maven lifecycle</li>
		<li>Integrate the Scala console with maven's dependency resolution</li>
		<li>Integrate Scala documentation generation with the doxia</li>
	</ul>
	</li>
	<li>scm: git://github.com/davidB/maven-scala-plugin.git (browse <a href="http://github.com/davidB/maven-scala-plugin/tree/master">http://github.com/davidB/maven-scala-plugin/tree/master</a>)</li>
	<li>contributors:
	<ul>
		<li>David Bernard</li>
		<li>David Pollak</li>
		<li>Jesse Eichar</li>
		<li>Arnaud Bailly</li>
		<li>Josh Suereth</li>
	</ul>
	</li>
</ul>

<h5>scala-mojo-support</h5>

<ul>
	<li>Status - alpha</li>
	<li>Goals
	<ul>
		<li>Enable scala-defined Mojos to execute within a maven lifecycle</li>
	</ul>
	</li>
	<li>scm: git://github.com/jsuereth/scala-mojo-support.git</li>
	<li>contributors:
	<ul>
		<li>Josh Suereth</li>
	</ul>
	</li>
</ul>

<h5>Eclipse Maven Scala Integration (ESMi)</h5>

<ul>
	<li>Status - planning</li>
	<li>Goals
	<ul>
		<li>Integration with IAM and SDT</li>
		<li>Integration with M2E and SDT</li>
	</ul>
	</li>
	<li>Project Page: <a href="http://code.google.com/p/esmi/">http://code.google.com/p/esmi/</a></li>
	<li><em>Note: Currently Inactive.  All active efforts are being directed at SDT patches and maven-scala-plugin patches</em></li>
</ul>

<h5>lafros-maven-proguard-plugin</h5>

<ul>
	<li>Status - production</li>
	<li>Goals
	<ul>
		<li>&quot;Liberate&quot; jars with Scala-applets in mind</li>
	</ul>
	</li>
	<li>Project Page: <a href="http://code.google.com/p/lafros-maven-proguard-plugin/">http://code.google.com/p/lafros-maven-proguard-plugin/</a></li>
	<li>Contributors:
	<ul>
		<li>Rob Dickens</li>
	</ul>
	</li>
</ul>

<h5>scala-archetype-simple</h5>

<ul>
	<li>Status - outdated</li>
	<li>Goals
	<ul>
		<li>provide a simple archetype for scala project with sample tests in JUnit and in <a href="http://code.google.com/p/specs/">Specs</a></li>
	</ul>
	</li>
	<li>scm: <a href="http://github.com/davidB/scala-archetype-simple/tree/master">http://github.com/davidB/scala-archetype-simple/tree/master</a></li>
	<li>contributors:
	<ul>
		<li>David Bernard</li>
	</ul>
	</li>
</ul>