incubator-kitty-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From msacks <>
Subject Building kitty
Date Thu, 23 Dec 2010 20:54:50 GMT
I created a pom file and compiled with GMaven. I would like to propose
using GMaven for building and running tests because it seems like the
easiest way to go. Posting to the group for feedback. I am using the
standard gmaven-archetype-basic archetype for structuring my project.
I tried running it and got the following error:

Mfizzle:src msacks$ java -version
java version "1.6.0_22"
Java(TM) SE Runtime Environment (build 1.6.0_22-b04-307-10M3261)
Java HotSpot(TM) 64-Bit Server VM (build 17.1-b03-307, mixed mode)

Mfizzle:mvn msacks$ mvn compile
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Example Project
[INFO]    task-segment: [compile]
[INFO] ------------------------------------------------------------------------
[INFO] [groovy:generateStubs {execution: default}]
[INFO]  Generated 2 Java stubs
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 4 source files to /Users/msacks/kitty/mvn/target/classes
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

cannot access junit.framework.TestCase
class file for junit.framework.TestCase not found
public class ClientTest

package org.apache.kitty.utils does not exist

I have attached the project + pom here:

I suggest we should evaluate both GMaven and Gradle and just see what fits best.

View raw message