Maven on cat /dev/snapshot

Use Java 7 on Buildhive

Tue, 14 Aug 2012 14:09:00 +0200

Changing source and target version to 1.7 is not sufficient to enable Java 7 on Buildhive at the moment.
Adding the following profile to your Maven POM makes sure that your local build is not affected by the special configuration and when running on Buildhive, JDK 7 is used for both build and test-run.

  <profiles>
    <profile>
      <id>buildhive</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>2.5.1</version>
            <configuration>
              <source>1.7</source>
              <target>1.7</target>
              <showDeprecation>true</showDeprecation>
              <showWarnings>true</showWarnings>
              <encoding>UTF-8</encoding>
              <executable>/opt/jdk/jdk1.7.0/bin/javac</executable>
              <fork>true</fork>
            </configuration>
          </plugin>
          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <configuration>
              <jvm>/opt/jdk/jdk1.7.0/bin/java</jvm>
              <forkMode>once</forkMode>
            </configuration>
          </plugin>
        </plugins>
      </build>
    </profile>
  </profiles>

The profile can be selected by adding the following line to the configuration of your Buildhive job:

Deploying weld-osgi to jcoderz.org repository

Sat, 31 Dec 2011 16:36:00 +0100

For deploying weld-osgi to the jcoderz.org repository the following modifications to the pom.xml files are necessary (after applying the wagon-ssh extensions to the your Maven installation, see previous post):

Deploy the WELD API packages

git clone -b WELD-963 http://github.com/mathieuancelin/api.git WELD-963
cd WELD-963
vi pom.xml

Add the following XMl fragment to the maven-deploy-plugin

   <build>
      <plugins>
         <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-deploy-plugin</artifactId>
            <configuration>
               <skip>true</skip>
            </configuration>
            <dependencies>
              <dependency>
                <groupId>org.apache.maven.wagon</groupId>
                <artifactId>wagon-ssh</artifactId>
                <version>2.2</version>
              </dependency>
            </dependencies>
         </plugin>
      </plugins>
   </build>

mvn -e clean install -Dmaven.test.skip=true
mvn -e deploy -DaltDeploymentRepository=jcoderz-snapshots::default::scp://jcoderz.org/var/www/repos/maven2-snapshot/ -Dmaven.test.skip=true
cd ..

2. Deploy the WELD OSGi packages

Maven 3: SSH deployment to foreign repository

Sat, 31 Dec 2011 16:08:00 +0100

Using the maven-deploy-plugin to deploy artifacts to a repository that is not the original target repository of a project is getting complicated with Maven 3 when the wagon SSH provider is not part of the Maven distribution. The following JAR files must be added to the Maven distribution into the lib/ext extension folder:

jsch-0.1.44-1.jar
plexus-utils-3.0.jar
plexus-interactivity-api-1.0-alpha-6.jar
wagon-ssh-2.2.jar\n* wagon-ssh-external-2.2.jar
wagon-ssh-common-2.2.jar

Then the parent pom.xml of the project must be extended by the following lines:

Building weld-osgi

Tue, 06 Dec 2011 23:11:00 +0100

In case you want to use Weld inside your OSGi application you first need to compile a few branches on your own:

WELD-963 branch of the weld/api project
weld-osgi branch from the weld/core project

Those branches will soon be merged into the official Weld codebase. But in the meantime you need to follow the steps below in order to get the packages compiled.
A prerequisite is that git and Maven 3 is available