(What follows assumes a certain level of understanding for Maven AND Hudson...AND what I learnt to get site-deploy goal a going within Hudson!)

The project had a goal - site-deploy that I wanted to execute within Hudson. Within my pom.xml, I had the following:

    <distributionManagement>
     <site>
       <id>remoteserver</id>
       <url>scp://some.server/var/www/maven/site</url>
     </site>
   </distributionManagement>

In order to make the scp work, you need the following in your USER_HOME/.m2/settings.xml:

    <servers>
      <server>
         <id>remoteserver</id>
         <username>whatuser</username>
         <password>whatuser</password>
         <filePermissions>664</filePermissions>
         <directoryPermissions>775</directoryPermissions>
      </server>
    </servers>

Let's assume you have completed the multi-step task of creating a new job within Hudson and it executes your site-deploy goal. Just when you thought it was safe to enter the water...WHAM!!!...you get hit with the error:

[INFO] [site:deploy]scp://remoteserver/var/www/maven/site/your.project - Session: Disconnecting
        scp://remoteserver/var/www/maven/site/your.project - Session: Disconnected
[HUDSON] Archiving /whatever...project...path/pom.xml to /whatever...project...path/builds/2008-10-07_16-01-29/whatever.../pom.xml
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error uploading site
Embedded error: The host was not known and was not accepted by the configuration: remoteserver
reject HostKey: remoteserver

Try as I might to overcome this, I couldn't...at least not within Hudson! At least for my configuration, when Hudson executed my Maven2 projects, it will run as root (you can tell 'cuz the Maven repository is stored in /root/.m2/repository). So do this:

whatuser@remoteserver:~$ sudo -i

root@remoteserver:~$ cd /path/to/mvn/project

root@remoteserver:/path/to/mvn/project$ mvn clean site-deploy

Accept the authentication and wait for the build to complete and deploy. If you are to run Hudson now, it will work.

Huh? What happened? The reason can be found here. In other words, Hudson could not deploy because it could not authenticate and accept the remote connection!

Well, I hope the above helps save some hours for those in the similar predicament!

I will assume you have finished reading Using Maven 2 to create a project and Maven project directory layout, logging.

To be continued...

available here and here

Thanks for looking!  Take good care and I'll see you back here tomorrow.

Since I'm pretty gnu to seam/jsf, I decided to start with seam-numberguess-2.1.0.CR1.ear and put it back together again.

Sadly, this process didn't result in a completely clean solution... in the end I couldn't quite get the ear plugin to do what I wanted and ended up overriding the application.xml, jboss-app.xml, jamming some stuff into a lib dir in the ear etc.. Hope to clean it up at some point.

Perhaps you can get softeu to work for you... for me it just blowed up in various interesting ways...

multiproject

groupId=jsf-in3
package=us.versus.them.demos.jsf.in3
version=1.0.0-SNAPSHOT
common="-DgroupId=${groupId} -DpackageName=${package} -Dversion=${version}"
webapp=-DarchetypeArtifactId=maven-archetype-webapp

mvn archetype:create ${common} -DartifactId=in3-project
cd in3-project
cat pom.xml | sed 's,>jar<,>pom<,' > fu
mv fu pom.xml
mvn archetype:create ${common} -DartifactId=in3-jar
mvn archetype:create ${common} ${webapp} -DartifactId=in3-war
mvn archetype:create ${common} ${webapp} -DartifactId=in3-ear

Unfortunately, there is a lot more junk that has to be done by hand... Stuff that is really pretty dumb.

java 5, please

    <build>
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-compiler-plugin</artifactId>
                    <configuration>
                        <source>1.5</source>
                        <target>1.5</target>
                    </configuration>
                </plugin>
            </plugins>
        </pluginManagement>
    </build>

jboss repo

    <repositories>
        <repository>
            <id>central</id>
            <name>Maven Repository Switchboard</name>
            <layout>default</layout>
            <url>http://repo1.maven.org/maven2</url>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
        </repository>
        <repository>
            <id>jboss</id>
            <name>JBoss Maven Repository</name>
            <layout>default</layout>
            <url>http://repository.jboss.org/maven2</url>
            <snapshots>
                <enabled>false</enabled>
            </snapshots>
        </repository>
    </repositories>

war: wtf is it good for?

So I pulled the goodies out of the war and put them in their maven-ish spots:

.
|-- pom.xml
`-- src
    `-- main
        |-- resources
        |   `-- messages.properties
        `-- webapp
            |-- WEB-INF
            |   |-- components.xml
            |   |-- pages.xml
            |   `-- web.xml
            |-- cheat.jspx
            |-- confirm.jspx
            |-- giveup.jspx
            |-- index.html
            |-- index.jsp
            |-- jboss-seam-numberguess.war
            |-- lose.jspx
            |-- niceforms.css
            |-- niceforms.js
            |-- numberGuess.jspx
            `-- win.jspx

there is a also a "images" directory under webapp I left out, cuz it's kinda boring.

This structures is a little lame, but I don't wanna change too much right now...

war deps

There are a two deps that I resolved to something like this:

  <dependency>
      <groupId>commons-beanutils</groupId>
      <artifactId>commons-beanutils</artifactId>
      <version>1.7.0</version>
  </dependency>
  <dependency>
      <groupId>jboss</groupId>
      <artifactId>jboss-seam-ui</artifactId>
      <version>2.0.0.BETA1</version>
  </dependency>

jar it

mkdir -p src/main/resources
touch src/main/resources/seam.properties

seam.properties has to end up in the root of the jar or seam will not work!!!! it will be broken!!! even though it is just a dumb empty properties file!!!! don't forget it!!!!

You will end up with a nasty bit like:

javax.servlet.ServletException: Expected a child component type of UISelectItem/UISelectItems for component type javax.faces.SelectOne(selectGuessRadio).  Found null.

and even if you hack the jspx you will end up with something like:

javax.servlet.ServletException: /numberGuess.jspx(42,82) '#{numberGuess.currentGuess}' Target Unreachable, identifier 'numberGuess' resolved to null

And you may tear your hair out! And you may gnash your teeth! And when you find out the problem you may want to post it on your blog so noone else will have to suffer the same fate! I would imagine... ;-)

jar it up some more

mkdir -p src/main/java/org/jboss/seam/example/numberguess/
cp NumberGuess.java ${_}

I snagged mese'f a copy of NumberGuess.java

The biggest thing the tutorial left to the imagination was the imports:

import java.io.Serializable;
import java.util.ArrayList;
import java.util.List;
import java.util.Random;

import org.jboss.seam.ScopeType;
import org.jboss.seam.annotations.Create;
import org.jboss.seam.annotations.Name;
import org.jboss.seam.annotations.Scope;

Presumably in the interests of brevity...

jar deps

  <dependency>
      <groupId>jboss</groupId>
      <artifactId>jboss-seam</artifactId>
      <version>2.0.0.BETA1</version>
  </dependency>

ear is totally wrong

I dunno what else to say about it... Ended up redoing the whole pom and even then it wasn't right. The jboss-app.xml was always empty, I couldn't get it to quit being dumb about being smart about ejbModules...

In the end, I clobbered the generated application.xml and jboss-app.xml with the ones from the seam-numberguess-2.1.0.CR1.ear

cp pageflow.jpdl.xml cheat.jpdl.xml target/in3
cp jboss-app.xml application.xml target/in3/META-INF
jar cf in3.ear -C target/in3 .
mv in3.ear ${JBOSS_HOME}/server/default/deploy/

final product

As I said in the beginning this was not a 100% success, but it was a lot closer than when I started:

% wget http://brianin3d.googlepages.com/in3-project.tgz
% tar xfz in3-project.tgz
% cd in3-project
# this assumes you have JBOSS_HOME defined...
% mvn package &&  ( cd in3-ear/ ;  ./bother.sh )

Hit http://localhost:8080/seam-ng-mvn to see it in action.

A rough start, but at least it's a start... :-D

Well it turns out that in our setup Maven's using a surefire reports thing that only runs tests whose class names end in ...Test.  My classnames usually do, but for this multimodule example, they weren't really unit tests so I had called them BlahBlahExample.  (This worked fine to run them in Eclipse.)

So, I just renamed the classes to end in ...Test, and now my tests run when I Maven Install 'em.

(Thanks for the tip, Keith!)

Up and coming

• Neo4J - A graph store - no more ORMappings
• Qi4J - A composite development framework, a new way of writing Java applications, a way of life
• Groovy GRAILS - Excellent for prototyping Java stuff
• Mercurial - When thinking different, why not Version Control as well?
• Swing Appframework, Java6u10 - Propably the next big thing in Rich Internet Applications
• Visualization of graphs - Am looking for a nice, easy API for creating several hierarchical trees that I can drag and manipulate
• Amazon EC2 - Java enabled servers on demand!
• Twitter, Blog, IRC -New (and revisited) ways of communicating intra-project/company
• javaBin, JavaZone - Working with the JavaZone conference for a year was damn fun!
  

Same old

Knowledge Sharing, Wiki, Ideas, Architecture, RFID, Sun Spot, Music, Topic Maps, Maven, Linux, OS X, Continous Integration, Mockito, Testng, REST

Moving away from

Hibernate, Spring, Web, Integration, Grid Frameworks, Web Services, Windows

Current projects

• Music DJ program
• Neo4JDemo
• AnarQi4JDemo - Qi4J
• JavaZone RFID applications

Closed projects

• Web applications on demand - Gigaspaces , web apps
• Kvittr - Grails, posting sms and emailing based on an RSS Feed
• Ultimate Roundtrip - A scaffold for improving development roundtrip for web applications with Maven, embedded Jetty and JWebunit webtests
• Webugger - Embedding a Groovy console efor debugging web and applications with high roundtrip

//Setting up the database in a folder called myNeoDB
NeoService neoDb = new EmbeddedNeo("myNeoDB");
//Create test dataset
Node neo = neoDb.createNode();
neo.setProperty("name", "Thomas Andersson");
Node trinity = neoDb.createNode();
neo.createRelationshipTo(trinity, MyRelationShipTypes.KNOWS);


Queries can be done with SPARQL, or a traverser:

Traverser friendFinder(Node person) {
return person.traverse(
Traverser.Order.BREADTH_FIRST,
StopEvaluator.END_OF_NETWORK,
ReturnableEvaluator.ALL_BUT_START_NODE,
MyRelationShipTypes.KNOWS,
Direction.OUTGOING);
}


The Matrix demo is as simple as Unzip og "mvn test"!

Me no like 32 repetitions of same thing.

So I looked for a way to do it from the command line.

Here's a way that worked for me:

(I ran the following once from the project's src/main/java, and once from src/test/java)

[sourcecode language='php']

svn propset -R svn:keywords "Author Id Revision Date" .

[/sourcecode]

Part of why this works so easily is that, guided by the Maven defaults, we're set up with our Java source code split out from the other files into src/{main,test}/java.  If the XML configuration files were in the same directory with Java source code, it would take more work to set the property on just the Java files, I think.

<build>
<plugins>
<plugin>
<groupId>info.flex-mojos</groupId>
<artifactId>flex-compiler-mojo</artifactId>
<configuration>
<mergeResourceBundle>true</mergeResourceBundle>
<allowSourcePathOverlap>true</allowSourcePathOverlap>
<includeResourceBundles>
<bundle>WorkFlowModuleLib</bundle>
</includeResourceBundles>
<locales>
<locale>en_US</locale>
<locale>ar_AE</locale>
</locales>
</configuration>
</plugin>
</plugins>
</build>

The version of flex-compiler-mojo used is 2.0M5

I then did a Maven Install on the multimodule parent project, and then a Maven Eclipse on the service module project, expecting that now the service module would see the interface changes in the domain module's interface... but 'tweren't so.

Something that Worked

I then did a Maven Install of the domain module.  Now when I Maven Eclipsed the service module, I got the interface changes from the domain module.

This is all probably normal -- just noting it in case I get confused again later...

Flex is a great platform for developing RIA (Rich Internet Applications), Maven 2 is known for its maturity and versatality in managing dependencies and in terms of project management and Java 2 is a mature technology for developing server side components (Java JEE). JBoss is a light-weight Open Source application server which is fully compatible with the Java EE5 standards that can be used both in development and production environments for deploying enterprise j2ee applications. You can download one from here
JBoss-Download

Putting all these together can be quite a challenge. However, we are not alone. We have enthusiast from various corners to help us in achieving our goals.

I personally use a linux box loaded with opensuse 11.0 with a bare minimum set of softwares installed to keep the development up and running.

Following are the list of softwares installed in my local box.

1. FlexBuilder3 eclipse plugin for Linux Alpha 4. You can download here
FlexBuilder-Linux
2. MySQL 5.0.67. You can download the source tar ball here
MySQL-source-download

3. Eclipse 3.3 (Europa)

4. Maven Integration for Eclipse

Maven-Integration-for-eclipse

5. Sub Version Eclipse Plugin SubVersion-Eclipse-Plugin

6. JBoss 4.2.3.GA (JDK 6)

and I am ready to go.

Notes:

Integrating maven with flex projects was a pain not before I discovered flex-mojos (http://svn.sonatype.org/flexmojos/) which are essentially maven plugins to compile flex sources like .mxml / .as / .css into concrete artifacts like .swf / .swc etc. You can visit the following blog to get more information about flex-mojos and the various options available there (http://blog.flex-mojos.info/). There were other resources like israfil-mojo which did almost the same job. However, in my personal opinion, I would prefer flex-mojos which is more complete and stable compared to israfil mojos.

MySQL is a light-weight RDBMS software which can aptly fit into any development environment. Coupled with some utilities like MySQL-Administrator and MySQL-QueryBrowser, it forms a perfect match for low-cost, productive development environment setup. You may experiment more with the source available here (http://dev.mysql.com/get/Downloads/MySQL-5.0/mysql-5.0.67.tar.gz/from/http://ftp.iij.ad.jp/pub/db/mysql/)

Installing MySQL on Linux could be tricky for newbies. For those who are new to linux and mysql, the following post might prove useful.

http://laffers.net/howtos/howto-install-mysql

Granite Data Services is one another open-source framework for integrating flex and java using AMF protocol for serialization / de-serialization of action script classes to java classes and vice-versa. You can visit the following site for more details

Granite Data Services

Details of how to setup a multi-module maven project using the above mentioned tools and softwares will form the primary content of Part - II of this post.

Till then, have fun.

Sriraman.

Background and Analysis

The ojdbc5 artifact was listed in the project's pom file as a compile-scope <dependency> under a certain profile.  That profile was activated by our CI server when deploying schema changes, because Liquibase needed it around.  That was why the .war was sometimes built with ojdbc5 in it and sometimes not.

The config has been this way for several weeks, but we didn't notice it until we just in the last few days got to the point of contributing Hibernate mappings, which then needs ojdbc to actually work.  At that time, the ojdbc jar in the war file fought with the ojdbc jar in JBoss's server/default/lib directory, and just like when you were fighting with your sister over that cookie, nobody won and we got the NoClassDefFoundError.

So we needed ojdbc5 to be around at build time (at least when a certain Maven profile is active), but not be included in the war file.

First Fix

Our first fix was to declare the ojdbc5 artifact as an extension for the build instead of as a dependency of the profile.  That worked (that is, it allowed the build to succeed and didn't put the ojdbc5 jar in the resulting war file), but it made the ojdbc5 artifact available to all builds of our war file, meaning we could accidentally start depending on ojdbc to be there.  While not a stopper, it wasn't ideal.

Final Fix

It turns out that by declaring ojdbc5 as a test-scope dependency in the profile where it was originally was (the one that is only active when we're deploying schema changes), we get all three things we wanted

• ojdbc5 is around at build time if and only if that one Maven profile is active
• ojdbc5 is never included in the war file

Some tools/plugins/features in Eclipse may need to use a JDK rather than a JRE. Sometimes you may even wish to switch between different versions of the JRE or JDK being used since typically 1.4, 1.5/5 and 1.6/6 are all present on a developers' system at different locations.

I got a mesage from a Maven plugin which said that it needed a JDK to be used to run Eclipse instead of a JRE that it was currently using. Well, this shouldn't usually present much of a problem. You can choose the virtual machine used to run Eclipse by passing the -vm argument to eclipse.exe. What's usually needed is something like "eclipse.exe -vm c:\jdk1.6\bin\javaw.exe". Mind you, javaw.exe is used when you don't want an associated console window.

I did have JDK 1.6 installed. But it was installed to "C:\Program Files\Java\jdk1.6.0_07". That, it seems, is the default location. The space in the path caused big problems. I tried quotes\no quotes and other magical incantations to get it to accept the argument with a space but to no avail.

So instead of using the command line switch, I put an entry into eclipse.ini which is in the same directory as eclipse.exe. But this didn't work either.

Finally, what did work was that I started command.exe (the 16 bit DOS shell) and navigated to the JDK directory using "dir /X" for help which shows names generated in the format "C:\PROGRA~1\JAVA\JDK16~1.0_0\BIN". Perhaps you remember coming across such filenames.

Anyway, the older 8.3 style directory name worked! My final eclipse.ini is posted below.

-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256M
-framework
plugins\org.eclipse.osgi_3.4.0.v20080605-1900.jar
-vm
C:\PROGRA~1\JAVA\JDK16~1.0_0\BIN
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m

I was using Windows XP with SP3 and Eclipse 3.4. There is likely to be a better solution that I missed. If you have it or if this post helped you, please leave a coment. :)

org.apache.maven.BuildFailureException: Project 'com.example.training.framework-test-harness-example:framework-test-harness-example-db' is duplicated in the reactor

I looked around and around in the pom files, but it was Keith who spotted it:

I had given the domain module an artifactId of framework-test-harness-example-db instead of framework-test-harness-example-dmn -- classic copy-n-paste error!

I had created the parent project with its pom, pointing to the production great-grandpappy pom that has all the dependencyManagement stuff (external dependencies, versions, etc.)

I had created a child project under the parent project, and made a pom for it pointing to the parent project's pom.

I had made a <module> entry in the parent pom pointing to the child module, and also a <dependency> entry pointing to the same.

I had done a Maven Install on the parent project, to get it into my local Artifactory repository.

I had done a Maven Eclipse on the child project, bringing in the just-installed parent project and all the dependencies.

Nothing Happens

Flushed with success, I tried to extend ModuleStarter, one of the classes provided by the pom files.  As expected, the class was not recognized, so I Ctrl+Shift+O'd it, but...nothing happened.

What could it be?  I pressed Ctrl+Shift+O several more times; looked at the pom files; checked the Referenced Libraries (and yes, the class was there!) ...

I spent many minutes on this, until I tried (again) to type out the fully-qualified name of the class I was extending.  The red "this did not work" underlining did not go away, but this time I hovered the mouse over the class name to see what the error details were, to wit:

The type ModuleStarter cannot be the superclass of BlahBlah; a superclass must be a class

A different magic word

A superclass must be a class... a superclass must be a class... it took a few moments for the meaning of this to sink in, but then it hit me: ModuleStarter is not a class, it's an interface.  Ha!

So I just had my class say implements instead of extends ModuleStarter, and now Ctrl+Shift+O works again, and peace and happiness have returned to my multimodule project.

*I first played Will Crowther's Colossal Cave text-based adventure game off of a 5.25" 360K floppy disk on my family's 8088 PC, in high school.  The influence of this game on me rivals that of Scooby-Doo cartoons in the '80s!  In that game, a common exchange (for me anyway) was:

>xyzzy
Nothing happens.

maven 是啥? 簡單來說可以稱為一個方便的" build tool" 幫我們省去很多工作。包含Ant 會做的事: compile, 打包(packing), test(測試) , distribute(發佈)。另外可以跑報表, 生成 web site, 更有彈性的 team work.

透過POM (project object model)設定，就可以方便來管理專案

來看看官方網站對 maven 的敘述

恩  此時 maven 已經裝好了

mvn archetype:create -DgroupId=com.mycompany.app -DartifactId=my-app
在目前的目錄下 就會幫你建立一個資料夾，到 my-app 看一下吧
cd my-app
會看到如下的結構
my-app
|-- pom.xml
`-- src
    |-- main
    |   `-- java
    |       `-- com
    |           `-- mycompany
    |               `-- app
    |                   `-- App.java
    `-- test
        `-- java
            `-- com
                `-- mycompany
                    `-- app
                        `-- AppTest.java

這個結構就是maven 預設的結構。src 底下分為 main, test 。java 底下才開始是package, class。
pom.xml 就是maven 核心了。
回頭來看剛剛下的指令  archtype:create
這是第一個學到的指令我們稱為 maven goal ，create 顧名思義就是幫我們建立專案，後面的參數都是用 -D 開始的。
groupId，你看到就是你的package 。artifactId，就是你專案位置
接下來 run 一下吧 先到你剛剛建立的專案下面, 有pom.xml 的地方
mvn:install
maven 開始幫你create, compile, test, package 最後會幫妳出一個 jar file
你會發現多一個資料夾 target ，裡面有一個jar file 就是最後的產出物
java -cp target/my-app-1.0-SNAPSHOT.jar com.bt.maven.App
回頭來看你的電腦檔案
~/.m2/repository,  ~/.m2/setting.xml (~/.--> C:\Documents and Settings\'yourname'n or C:\Users\'yourname') 會多出這些東西。
這裡就是 maven 的储藏庫。

In the face of a mystery like this, I tend to wax philosophical, pondering: "How can this be?"

Well, let's dig in and see if we can figure it out.

Digging In

I can reproduce the issue by doing a local Maven Install.  (Guess it would be a good idea to do one of those before committing my changes, huh? :)  The output looks something like this:

[sourcecode language='php']
...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

C:\path\to\eclipse-workspaces\production\framework-test-harness\src\main\java\com\example\fw\testutil\ConfigurationSwappingAbstractTestCase.java:[7,24] package org.junit.runner does not exist

C:\path\to\eclipse-workspaces\production\framework-test-harness\src\main\java\com\example\fw\testutil\ConfigurationSwappingAbstractTestCase.java:[8,25] package org.junit.runners does not exist

C:\path\to\eclipse-workspaces\production\framework-test-harness\src\main\java\com\example\fw\testutil\ConfigurationSwappingAbstractTestCase.java:[9,39] package org.junit.runners.Parameterized does not exist
...
[/sourcecode]

Now how's come the org.junit.runner package doesn't even exist?

This smelled like a pom file issue...and indeed it was.

Normally Test Scope is Right...

We have a parent pom file that brings in certain libraries for every project, and JUnit 4 is one of those.  It is declared at test scope, because we normally wouldn't want to ship the JUnit library, or any tests that depend on it.

...But This is a Little Different...

That's where our framework test harness is a little different: this project's purpose is to provide services for use by other projects' integration tests, and as part of that it provides a base class that uses JUnit annotations.  So our framework test harness actually has a compile-scope dependency on JUnit rather than the normal test scope dependency.

Solution

All I needed to do was update the test harness project's pom file and adjust the junit artifact's scope to compile, like this:

[sourcecode language='xml']
       
       
            junit
            junit
            compile
       
[/sourcecode]

...and now Maven Install finds the JUnit classes just fine.

So, I admit it: I earned my -10 points on the leader board fair and square.  : )

10 nice tips about using JavaScript (esp. jQuery) for improving website usability.

On September 30, 2008 starts a (free?) webinar about writing Eclipse RCP applications.