Re: hsql DB startup

On Thursday 06 January 2005 02:28 am, Janos Mucsi wrote: This is not a strictly Maven question. Hi Jake This sounds very interesting. I have two questions: 1. Is testing against an in-process database a better idea than using mock-objects to fake Connection, ResultSet, etc? (I need to test

Re: hsql DB startup

I set up the HSQL database in the JUnit TestSetup. This drops and re-creates the database for each test class that need the database, but the overhead is quite low, only a few test classes need the database running, and it ensures left over database artifacts will not have any side-effects on

Re: hsql DB startup

individually or does the Suite get executed and then it runs the tests? Just curious, I just didn't know how that part of the test framework of maven worked. Thanks again. Charlie Jake Ewerdt said the following on 1/5/2005 3:09 PM: I set up the HSQL database in the JUnit

Re: hsql DB startup

This is why and how we use HSQL for testing. - It is much faster for developers who are in the habit of continuous testing to use HSQL instead of (for example) Oracle. - We don't have enough Oracle resources (connections, accounts, cpu) to support all the developers using it for continuous

Checkstyle source directory

I am preprocessing my src directory using Jass into target/src-jass. My pom.build.sourceDirectory and maven.src.dir values are set to target/src-jass, and I have a preGoal on java:compile that preprocesses the src dir. This is fine for every case except Checkstyle, since Jass messes up the

Linkcheck and FindBugs OutOfMemoryError

I'm getting a java.lang.OutOfMemoryError when running the Linkcheck and FindBugs plugins on my project. I have these env vars set: export JAVA_OPTS=-mx1024m export ANT_OPTS=-Xmx1024m export MAVEN_OPTS=-Xmx1024m Here are the errors: maven-linkcheck-plugin: Not using a proxy Found 0 files so

Re: javadoc plugin

Yeah, same thing happened to me. I modified the javadoc's plugin.jelly to get it working. Here's the diff: 93,94c93 packagenames=${pom.package} sourcepath=${pom.build.sourceDirectory} --- packagenames=${pom.package}.* 109a108,124 ant:fileset

Re: maven jelly tag and build.properties properties

I've had various problems when the variable has a . or - in it. I use a workaround like this: property name=buildnumber value=${build.number} / j:if test=${empty(buildnumber)} failUsage: maven -Dbuild.number=x releaseNotes/fail /j:if If I put j:if

Re: Problem running Maven on an Alpha using Compaq Tru64 UNIX V5.1B (Rev. 2650)

of the JVM were you using? I've currently using 1.4.1-1 but I believe I have access to other versions which I will be trying today and reporting on. I don't have the option to move to Linux for this process. Jake Ewerdt wrote: I had exactly the same problem with Maven (1.0-rc1) and Tru64

Re: Problem running Maven on an Alpha using Compaq Tru64 UNIX V5.1B (Rev. 2650)

I had exactly the same problem with Maven (1.0-rc1) and Tru64. I could run all ant tasks but no ant-optional tasks (junit, chown, replaceregexp, ...). I tried with ant 1.5.4 and 1.6. Spent a day or so trying to get it to work, and eventually gave up and moved everything over to Linux where

Java output

I need to capture the result of running the java task in the maven.xml file. The same code works in an ant build.xml file, and it should work in the maven.xml file. Java file package com.jake; public class Jake { public static void main(String []args) {

Re: Multiproject and jelly scripting

In my maven.xml file, I just reference them like ${pom.artifactId} ${pom.currentVersion} -jake On Tuesday 06 January 2004 07:36 am, Hahne, Ronald wrote: I need to write a jelly script at the top level of the multiproject which will optain the POM id and currentVersion of each of the

Deploy info

Where is the documentation on the deploy namespace? I found a reference to it in some documentation, but didn't find any documentation on it. I would like to know more about it and if it includes any more tags. This is how I am using it. project xmlns:deploy=deploy goal

Re: Where and how to set environment variables?

In the Ant Optional task documentation under JavaCC, it says you can set the javacchome variable for that task, so you wouldn't need an env var. If maven has a javacc plugin, but it won't take a property for javacchome, you'll have to modify the plugin.jelly for that plugin or just use the ant

Last Sequential File

I'm currenly working on moving a build system that comprises mainly of shell scripts to maven. One of the things that the current system does is create a changelog file (changelog.${build.number}) that contains all CVS commit logs since the last release. We use build numbers, but releases are

JUnitTask not found in test:test goal

Hello, I run maven test:test and I get this error: BUILD FAILED File.. file:/usr/users/jake/.maven/plugins/maven-test-plugin-1.4/ Element... junit Line.. 94 Column 39 org/apache/tools/ant/taskdefs/optional/junit/JUnitTask Total time: 11 seconds Finished at: Tue Dec 30 12:24:31 EST

Re: JUnitTask not found in test:test goal

the following to project.properties maven.junit.fork=yes Paul Spencer Jake Ewerdt wrote: Hello, I run maven test:test and I get this error: BUILD FAILED File.. file:/usr/users/jake/.maven/plugins/maven-test-plugin-1.4/ Element... junit Line.. 94 Column 39 org/apache