I am releasing a new plugin that helps you manage your use cases. It also
helps
you document the sequence information and generate the CRC cards.
You can find more information here.
http://www.itbrain.com.mx/ucdd
--
Humberto
Hi,
I recompiled maven changelog plug-in so that it works with CVS 1.12.9
log format. If anyone is also having the same problem, I'll post the
changes to the mailing list.
cheers,
Vincent
-
To unsubscribe, e-mail: [EMAIL
Thank you Jeff - it now works perfectly :)
Jesper Linvald
MAERSK DATA TRANSPORT
Tel no.: +45 3911 1891
e-mail: [EMAIL PROTECTED]
Jefferson K. French [EMAIL PROTECTED]
09-08-2004 19:04
Please respond to
Maven Users List [EMAIL PROTECTED]
To
Maven Users List [EMAIL PROTECTED]
cc
Subject
Re:
Is it compatible with older CVS release ??
Can you post it on Jira please?
Arnaud
-Message d'origine-
De : Vincent Zang [mailto:[EMAIL PROTECTED]
Envoyé : mardi 10 août 2004 08:27
À : Maven Users List
Objet : Fixes for Maven changelog plugin to work with CVS 1.12.9
Hi,
I
Hi,
I'm using JCoverage plugin and Junit plugin in the same project.
Junit report no failure and no error
Jcoverage report an error with the same testcase.
I've got a java.lang.VerifyError (Illegal constant pool index)
I'm using the following properties:
maven.test.failure.ignore=true
I have the following maven.xml file:
project xmlns:j=jelly:core
goal name=myGoal
j:forEach begin=1 end=5 indexVar=i
echo${i}/echo
exec executable=gcc
arg line= -DA=${i} test.c -o test.exe/
/exec
exec executable=test/
/j:forEach
Hi,
-Original Message-
From: ext Claus Pedersen [mailto:[EMAIL PROTECTED]
The file test.c :
int main()
{
int a = A;
printf(a = %i,a);
return a;
}
All the right values are returned, but why does it say
[ERROR] after the
execution?
My C(++) days lay years
Hi!
I think that you c code should return 0 as return value, usually other
than 0 means some error.
Artsi
ti, 2004-08-10 kello 13:53, Claus Pedersen kirjoitti:
I have the following maven.xml file:
project xmlns:j=jelly:core
goal name=myGoal
j:forEach begin=1 end=5 indexVar=i
Sorry my bad
Must have been drinking to much this weekend... :-)
The problem is solved...
I was returning an error code..
Hi,
-Original Message-
From: ext Claus Pedersen [mailto:[EMAIL PROTECTED]
The file test.c :
int main()
{
int a = A;
printf(a = %i,a);
Folks,
I currently have a project where the unit tests take a considerable amount of time to
run (5 minutes or so), and as a result, running them every time I do a build is
proving impractical. Initially, I just added the maven.test.skip flag to my
project.properties, but this isn't a good
How about just running maven java:compile? or, do maven
mybuild -Dmaven.test.skip=true
Eric
-Original Message-
From: Kenny MacLeod [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 2:49 PM
To: Maven Users List
Subject: Use of maven.test.skip
Folks,
I currently have a
You can override project properties on the maven command line:
maven -Dmaven.test.skip=false
If you have one environment where you want testing on by default and
another where you want it off set maven.test.skip as appropriate in
build.properties rather than project.properties.
Andy
Kenny,
You can create simple wrapper goals like this:
goal name=build-only
description=Build without running tests
j:set var=maven.test.skip value=true/
attainGoal name=jar:install-snapshot/
/goal
goal name=install
description=Build, run tests, and install
It is a workaround. Anyway it works so fine!
maven -o multiproject:clean
goal name=multiproject:clean
maven:reactor basedir=${basedir}
includes=**/${pattern}/**/project.xml
excludes=**/target/**/project.xml
Hi Mario, I followed Dion Gillard's suggestions and I created a customized
multiproject:cleam goal inside maven.xml of the my master project. This way:
goal name=multiproject:clean
description=[Ctp] Clean directories of all subprojects
echo[Ctp] ###
I recommend you forget that the flag exists and make the tests faster.
On Tue, 10 Aug 2004 13:49:06 +0100, Kenny MacLeod [EMAIL PROTECTED] said:
Folks, I currently have a project where the unit tests take a
considerable amount of time to run (5 minutes or so), and as a
result, running them
The maven team is pleased to announce the Maven Announcement Plugin 1.3
release!
http://maven.apache.org/reference/plugins/announcement/
The Announcement plugin generates release announcements. It uses the
information found in both the POM and in the changes.xml file to generate the
I wanted to define pom.siteDirectory in build.properties to overwrite
siteDirectory in project.xml to deploy to a different location, but it did
not work.
This is what I have in build.properties
...
maven.site.deploy.method=fs
pom.siteDirectory=C:/app/site
...
Maven build always uses the value
Liu, Zhihai wrote:
I wanted to define pom.siteDirectory in build.properties to overwrite
siteDirectory in project.xml to deploy to a different location, but it did
not work.
This is what I have in build.properties
...
maven.site.deploy.method=fs
pom.siteDirectory=C:/app/site
...
Maven build
Eric, thanks for the prompt response. It works.
-Original Message-
From: Erik Husby [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 4:11 PM
To: Maven Users List
Subject: Re: pom.siteDirectory
Liu, Zhihai wrote:
I wanted to define pom.siteDirectory in build.properties to
-Original Message-
From: Jeffrey D. Brekke [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 8:37 PM
To: Maven Users List
Subject: Re: Use of maven.test.skip
I recommend you forget that the flag exists and make the tests faster.
That doesn't necessarily help. If all of
hmm, my fingers are bad.
I meant, point test resource in your project.xml to the dummy one
On Tue, 10 Aug 2004 14:57:06 -0700, dan tran [EMAIL PROTECTED] wrote:
How about this! ;-)
Create 2 test suites. One is a dummy one, and the other one has all
tests you want to run.
Point test
On Tue, 10 Aug 2004 22:40:13 +0100, Charles Daniels [EMAIL PROTECTED] said:
I recommend you forget that the flag exists and make the tests
faster.
That doesn't necessarily help. If all of his tests take 0.1 second
on average, but he has 1000 tests, it still takes 100 seconds to run
them
Sory for this, I had forgotten the xmlns:castor=castor
Now I get another error when running the Castor generator :
castor:prepare-filesystem:
[echo] Generating sources for
D:\eclipse\workspace\crbt-metier\src\schemas\add_group_response.xsd
-- Suppressing non fatal warnings.
-- Disabling
24 matches
Mail list logo