Using Maven with Anthill

[Maciej Zawadzki]

Baz,

I've been playing around with getting Maven to work with Anthill. I used your posting on the Maven list as a starting point. Have you made any more progress on this?

Specifically, have you figured out how to make Maven use Anthill's version number? Also, how do you actually deploy the generated artifacts (java docs, etc.)? Looking at the maven-site-plugin-1.0/plugin.jelly, I see that maven tries to login to the host identified by pom.siteAddress using ssh, create the dir, scp the site over, and then unzip it. Judging by the maven.site.deploy.method=fs property in your Ant wrapper script, it seems that you were taking a different approach. Can the site:deploy goal simply copy the site to the pom.siteDirectory? Did you get that to work?

BTW, I cross posted this because I figured that both lists may benefit from the discussion.

Thanks,

--Maciej


--- Original post ---
Brian Ewins wrote:
Date: Thu, 28 Nov 2002 17:26:57 +0000
From: Brian Ewins <[EMAIL PROTECTED]>
Subject: Nightly build experiences?
Content-Type: text/plain; charset=us-ascii; format=flowed


Finally got maven+anthill working together, more details below, hope
folk find this useful - it works reasonably well. One thing I still need
to make this fully integrated is to get maven to use the version number
supplied by anthill. I'm trying to pass in "-Dpom.currentVersion=1.0.13"
(for example), but its getting ignored and I get the version from the
project.xml. Other properties, like pom.siteDirectory, seem to work.
This is b7 - is there a bug? Or have I got the name of the property wrong?

Cheers,
-Baz

How its done: I have a single build.xml (below) for all mavenized
projects sitting in the root of my anthill installation. All maven
projects get set up to use a build/publish script of "..\..\build.xml".
For build, I pass the extra arguments:
-Dmaven.goal=jar:install -Dmaven.project=myprojectname
and for publish:
-Dmaven.goal=site:deploy -Dmaven.project=myprojectname
My maven project.xml has currentVersion set to 'SNAPSHOT', so developers
only ever make snapshots; anthill is used for nightlies and releases.

<?xml version="1.0" encoding="UTF-8"?>

<project default="maven" name="mavenized" basedir=".">

<property environment="env"/>
<property name="env.MAVEN_HOME" value="C:\Program Files\Maven"/>
<property name="maven.goal" value="jar:install"/>
<property name="maven.project" value="MAVEN_PROJECT_NOT_SET"/>
<property name="maven.dir" value="${basedir}\work\${maven.project}"/>

<target name="maven" >
<echo message="Using MAVEN_HOME=${env.MAVEN_HOME} ${version}"/>
<java classname="com.werken.forehead.Forehead" fork="yes"
maxmemory="128m">
<arg value="-d" />
<arg value="${maven.dir}" />
<arg value="${maven.goal}" />
<classpath>
<pathelement
location="${env.MAVEN_HOME}\lib\forehead-1.0-beta-4.jar" />
</classpath>
<sysproperty key="maven.home" value="${env.MAVEN_HOME}" />
<sysproperty key="tools.jar"
value="${env.JAVA_HOME}\lib\tools.jar" />
<sysproperty key="forehead.conf.file"
value="${env.MAVEN_HOME}\bin\forehead.conf" />
<!-- persuade maven to use anthill's version -->
<sysproperty key="pom.currentVersion" value="${version}"/>
<!-- deploy the site into anthill -->
<sysproperty key="maven.site.deploy.method" value="fs"/>
<sysproperty key="pom.siteDirectory" value="${deployDir}"/>
</java>
</target>

</project>





--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>