[ANN] New Plugin for Use Case Driven Design
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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fixes for Maven changelog plugin to work with CVS 1.12.9
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 PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: FTP ant task
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: FTP ant task
What does it do when it doesn't work?
For me, the -X switch showed that there was a CNF exception for an oro
FTP class. I had to put this in my project.xml:
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version20020829/version
/dependency
dependency
groupIdoro/groupId
artifactIdNetComponents/artifactId
versionxxx/version
properties
classloaderroot/classloader
/properties
/dependency
The NetComponents JAR file is not at ibiblio, so I added it to our
company repo. The version 'xxx' I just added because there was no
version number associated with the JAR file.
In retrospect, the ant-contrib part may not be required. It looks like
the Ant FTP class is loaded automatically by Maven from
ant-optional-1.5.3-1.jar. I had to add the classloader property
because it looked like Ant's FTP class was loaded in the root
classloader, but the NetComponents JAR was loaded by the Maven
classloader. I know the classloader is deprecated, but I wasn't sure
how else to get it to work.
I did this in a plugin, so I added this to my plugin.jelly:
ant:taskdef name=ftp
classname=org.apache.tools.ant.taskdefs.optional.net.FTP
ant:classpath
ant:pathelement
path=${plugin.getDependencyPath('ant-contrib:ant-contrib')}/
ant:pathelement
path=${plugin.getDependencyPath('oro:NetComponents')}/
ant:path refid=maven.dependency.classpath/
/ant:classpath
/ant:taskdef
before invoking the ftp task. For a maven.xml file, you wouldn't use
${plugin}. I think you'd use ${context}, but I'm not positive.
Again, you may be able to drop the whole ant-contrib part.
Jeff
On Mon, 09 Aug 2004, at 12:40:51 [GMT +0200] Jesper Linvald wrote:
Hello all,
I am trying to use the ftp ant task from maven. It dosent work! Running
the task straight from Ant works fine
Some have suggested a brute hack with a typedef and dependency on Ant
1.6.
Before trying this I would like to hear if anybody has a solution to the
problem or another way to use ftp or scp?
Regards
Jesper Linvald
MAERSK DATA TRANSPORT
Tel no.: +45 3911 1891
e-mail: [EMAIL PROTECTED]
--
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : Fixes for Maven changelog plugin to work with CVS 1.12.9
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 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 PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JCoverage and Junit do not give same test result
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 maven.junit.fork=yes maven.junit.jvmargs=-Djava.awt.headless=true maven.compile.source=1.5 maven.compile.target=1.5 maven.jcoverage.junit.fork=yes Has anybody an idea of what happen? Best Regards Eric - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error in simple Maven build file
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
/goal
/project
The file test.c :
int main()
{
int a = A;
printf(a = %i,a);
return a;
}
It looks like it works... I get the right output from the function
Here is the Maven output:
build:start:
myGoal:
[echo] 1
[exec] a = 1
[exec] [ERROR] Result: 1
[echo] 2
[exec] a = 2
[exec] [ERROR] Result: 2
[echo] 3
[exec] a = 3
[exec] [ERROR] Result: 3
[echo] 4
[exec] a = 4
[exec] [ERROR] Result: 4
[echo] 5
[exec] a = 5
[exec] [ERROR] Result: 5
BUILD SUCCESSFUL
Total time: 2 seconds
All the right values are returned, but why does it say [ERROR] after the
execution?
I hope you have an answer.
Best regards,
Claus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error in simple Maven build file
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 behind me, but I think you are giving back an error code
(return a), that's why maven assums, that something went wront. try return 0 instead.
BR,
Andreas Ebbert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in simple Maven build file
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
echo${i}/echo
exec executable=gcc
arg line= -DA=${i} test.c -o test.exe/
/exec
exec executable=test/
/j:forEach
/goal
/project
The file test.c :
int main()
{
int a = A;
printf(a = %i,a);
return a;
}
It looks like it works... I get the right output from the function
Here is the Maven output:
build:start:
myGoal:
[echo] 1
[exec] a = 1
[exec] [ERROR] Result: 1
[echo] 2
[exec] a = 2
[exec] [ERROR] Result: 2
[echo] 3
[exec] a = 3
[exec] [ERROR] Result: 3
[echo] 4
[exec] a = 4
[exec] [ERROR] Result: 4
[echo] 5
[exec] a = 5
[exec] [ERROR] Result: 5
BUILD SUCCESSFUL
Total time: 2 seconds
All the right values are returned, but why does it say [ERROR] after the
execution?
I hope you have an answer.
Best regards,
Claus
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SV: Error in simple Maven build file
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);
return a;
}
All the right values are returned, but why does it say
[ERROR] after the
execution?
My C(++) days lay years behind me, but I think you are giving back an
error code (return a), that's why maven assums, that something went
wront. try return 0 instead.
BR,
Andreas Ebbert
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Use of maven.test.skip
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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? cheers kenny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Use of maven.test.skip
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 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? cheers kenny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use of maven.test.skip
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 [EMAIL PROTECTED] To: [EMAIL PROTECTED] 10/08/04 13:49 cc: Please respond toSubject: Use of maven.test.skip users 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? cheers kenny - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ For the latest data on the economy and society consult National Statistics at http://www.statistics.gov.uk ** Please Note: Incoming and outgoing email messages are routinely monitored for compliance with our policy on the use of electronic communications ** Legal Disclaimer : Any views expressed by the sender of this message are not necessarily those of the Office for National Statistics ** __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use of maven.test.skip
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 attainGoal name=jar:install-snapshot/ /goal Then just invoke the appropriate one. Jeff On Tue, 10 Aug 2004, at 13:49:06 [GMT +0100] Kenny MacLeod wrote: 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? cheers kenny -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
R: Multiproject:clean problem
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
goals=clean
banner= multiproject:clean
ignoreFailures=true/
/goal
Bye
-Messaggio originale-
Da: Milos Kleint [mailto:[EMAIL PROTECTED]
Inviato: lunedì 9 agosto 2004 15.34
A: Maven Users List
Oggetto: Re: Multiproject:clean problem
and what about the scenario when I do a multiproject clean the a
multiproject build which however failt mid-way.. a subsequent
multiproject clean failt, because it cannot resolve all dependencies..
is there a way out? it seems liuke one can only do a clean build after
successfully building the multiproject..
Milos
Dion Gillard wrote:
You typically need to do a multiproject:install or
multiproject:install-snapshot before using any other goals.
This places the dependent jars in the local repo.
On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro [EMAIL PROTECTED] wrote:
Hi, when I run Multiproject:clean in my master project, it tries to find a jar
file that was not created yet.
I use an argument passed to Maven (mm_domain) to create the name of jar file.
Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find
anything about this error.
Here is log:
+
| Executing clean:clean MM - SPBDns
| Memory: 3M/6M
+
Verifying dependencies for MM:spbdns
Getting failed dependencies: [EMAIL PROTECTED]
Attempting to download spbmessage-cetip-snapshot.jar.
Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar
Received status code: 404
File not found on one of the repos
java.io.FileNotFoundException:
http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar
at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181)
at
org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326)
at
org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255)
at
org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171)
at
org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97)
at org.apache.maven.project.Project.verifyDependencies(Project.java:1365)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:342)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at
org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:127)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
at
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at com.werken.werkz.WerkzProject.attainGoal(WerkzProject.java:193)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:634)
at
RE: Multiproject:clean problem
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] ### Running CtpMultiproject:Clean ###/echo
maven:reactor
basedir=${basedir}
banner=[Ctp] Gathering project list
includes=*/project.xml
postProcessing=true
ignoreFailures=true
collectOnly=true /
j:set var=mm_tag_version value=${mm_tag_version.toUpperCase()}/
j:forEach var=reactorProject items=${reactorProjects}
!-- this list of things to delete is lifted from clean:clean
--
j:if test=${mm_tag_version.equals('SNAPSHOT')}
ant:delete
dir=${reactorProject.context.getVariable('maven.build.dir')} /
/j:if
j:if test=${!mm_tag_version.equals('SNAPSHOT')}
ant:delete
dir=${reactorProject.context.getVariable('basedir')} /
/j:if
/j:forEach
/goal
goal name=mygoal
.
.
.
/goal
And, I run maven this way: maven multiproject:clean mygoal ... -Dmm_tag_version=$1
-Dmm_subprojects_name=spbmessage,mmserver,MM_Business,ispbdns -Dmm_domain=cetip
-Dmm_cvs_checkout=true -X | tee -a $HOME/MMmaster/mmlogs/$DATA
It worked perfectly.
Thanks a lot.
Best regards,
Roberto de Castro
Analista de Suporte
Cetip - Desus Rio de Janeiro
+55 21 2276-7439
mailto:[EMAIL PROTECTED]
-Mensagem original-
De: Stefanutti, Mario [mailto:[EMAIL PROTECTED]
Enviada em: terça-feira, 10 de agosto de 2004 14:12
Para: Maven Users List
Assunto: R: Multiproject:clean problem
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
goals=clean
banner= multiproject:clean
ignoreFailures=true/
/goal
Bye
-Messaggio originale-
Da: Milos Kleint [mailto:[EMAIL PROTECTED]
Inviato: lunedì 9 agosto 2004 15.34
A: Maven Users List
Oggetto: Re: Multiproject:clean problem
and what about the scenario when I do a multiproject clean the a
multiproject build which however failt mid-way.. a subsequent
multiproject clean failt, because it cannot resolve all dependencies..
is there a way out? it seems liuke one can only do a clean build after
successfully building the multiproject..
Milos
Dion Gillard wrote:
You typically need to do a multiproject:install or
multiproject:install-snapshot before using any other goals.
This places the dependent jars in the local repo.
On Mon, 9 Aug 2004 10:24:04 -0300, Roberto Castro [EMAIL PROTECTED] wrote:
Hi, when I run Multiproject:clean in my master project, it tries to find a jar
file that was not created yet.
I use an argument passed to Maven (mm_domain) to create the name of jar file.
Is there a bug in Multiproject:clean? I've looked up in faq but I didn't find
anything about this error.
Here is log:
+
| Executing clean:clean MM - SPBDns
| Memory: 3M/6M
+
Verifying dependencies for MM:spbdns
Getting failed dependencies: [EMAIL PROTECTED]
Attempting to download spbmessage-cetip-snapshot.jar.
Getting URL: http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar
Received status code: 404
File not found on one of the repos
java.io.FileNotFoundException:
http://laranjeiras:8080/maven/MM/jars/spbmessage-cetip-snapshot.jar
at org.apache.maven.util.HttpUtils.retrieveArtifact(HttpUtils.java:547)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:381)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:287)
at org.apache.maven.util.HttpUtils.getFile(HttpUtils.java:181)
at
org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:326)
at
org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:255)
at
org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:171)
at
org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:97)
at org.apache.maven.project.Project.verifyDependencies(Project.java:1365)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:510)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:266)
at
Re: Use of maven.test.skip
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 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? I think you may be onto something here. If they are so long, maybe they aren't unit tests and should be moved. -- = Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Announcement Plugin 1.3 released
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 announcement text. Changes in this version include: New Features: o Added check to verify that the POM has a versionelement for the announcement to be generated. Issue: MPANNOUNCEMENT-14. Thanks to Felipe Leme. o Added new optional maven.announcement.encodingproperty that defines which charset encoding to use to generate the text announcement (defaults to UTF-8). Issue: MPANNOUNCEMENT-13. Thanks to Felipe Leme. o Added new announcement:mailgoal to automatically send the generated announcement by email. Issue: MPANNOUNCEMENT-9. Thanks to Felipe Leme. o Added new optional maven.announcement.stylesheet.pathproperty that defines what stylesheet to use to generate the text announcement. Issue: MPANNOUNCEMENT-11. Thanks to Felipe Leme. Fixed bugs: o Fixed error message when current version is not available at xdocs/changes.xml. Issue: MPANNOUNCEMENT-12. Thanks to Felipe Leme. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-announcement-plugin -Dversion=1.3 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-announcement-plugin-1.3.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom.siteDirectory
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 for siteDirectory in project.xml and ignores my change in build.properties. Any help is greatly appreciated. This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: pom.siteDirectory
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 always uses the value for siteDirectory in project.xml and
ignores my change in build.properties.
Any help is greatly appreciated.
Put in the pom something like
siteDirectory${siteDirectory}/siteDirectory
Then put a default value in project.properties
siteDirectory=defaultSite
Then put in build.properties
siteDirectory=c:/app/site
--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard
Rm. 2192 320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: pom.siteDirectory
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 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 for siteDirectory in project.xml and
ignores my change in build.properties.
Any help is greatly appreciated.
Put in the pom something like
siteDirectory${siteDirectory}/siteDirectory
Then put a default value in project.properties
siteDirectory=defaultSite
Then put in build.properties
siteDirectory=c:/app/site
--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard
Rm. 2192 320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Use of maven.test.skip
-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 his tests take 0.1 second on average, but he has 1000 tests, it still takes 100 seconds to run them all, which may still be unacceptably long to wait when running frequently. 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 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? I think you may be onto something here. If they are so long, maybe they aren't unit tests and should be moved. -- = Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use of maven.test.skip
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 resource in your project.xml so that maven will invoke after compilation. it happens very fast since no test to run. Create a goal in your maven.xml to run your real test suite using test:single goal. and run it any time you want -D On Tue, 10 Aug 2004 22:40:13 +0100, Charles Daniels [EMAIL PROTECTED] wrote: -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 his tests take 0.1 second on average, but he has 1000 tests, it still takes 100 seconds to run them all, which may still be unacceptably long to wait when running frequently. 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 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? I think you may be onto something here. If they are so long, maybe they aren't unit tests and should be moved. -- = Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Use of maven.test.skip
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 all, which may still be unacceptably long to wait when running frequently. Then they would still be too slow I guess. There are projects with many more than 1000 tests that run in a reasonable time ( http://jakarta.apache.org/commons/collections/junit-report.html ). Everyone has a threshold wrt build times. Maven runs the tests on each build because that is a best practice in our industry. They should be fast and focused tests, otherwise maybe the build should not be dependant upon them ( the slow ones that is, in which case you could move them into a separate testing project ). In my experience, slow running tests usually have external dependencies ( files, database, network ) which slow them down. I try to have unit/programmer tests not depend on anything external. Those tests ( that depend on external systems ) are important, and should exist. But having the build depend on them may not be wise. This has been discussed on this list before, sorry if I came off too harsh, I was really trying to help. 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 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 solution, mainly because if I explicitly want to run the unit tests, I have to take the flag out again. What I want is for the unit tests not to be run when i do a build, but I do want them to run if I explicitly say so. The interactions between the Java and Test plugins don't seem to be flexible enough to allow this. My current solution is to move the unit tests out to a seperate project, but that seems like an arse-backwards way of going about it. Can anyone suggest a better approach? I think you may be onto something here. If they are so long, maybe they aren't unit tests and should be moved. -- = Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: use of castor plugin
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 generation of Marshalling framework methods (marshall, unmarshall,
validate).
BUILD FAILED
File.. C:\Documents and
Settings\ndeloof\.maven\cache\maven-castor-plugin-1.2\plugin.jelly
Element... ant:java
Line.. 92
Column 38
java.lang.NoClassDefFoundError: sun/reflect/ConstructorAccessorImpl
Total time: 6 seconds
Any idea ? Notice I use SUN jdk 1.4.2 and that I can run the generator from command
line without troubles.
Nico.
Hi,
can someone help me using castor plugin ?
I've added this in my maven.xml :
attainGoal name=castor:prepare-filesystem/
castor:generate schema=${schema} package=${package} marshal=false/
And I get :
SAXParseException: The prefix castor for element castor:generate is not bound.
What did I miss ?
Nico.
Our name has changed. Please update your address book to the following format:
[EMAIL PROTECTED].
This message contains information that may be privileged or confidential and is the
property of the Capgemini Group. It is intended only for the person to whom it is
addressed. If you are not the intended recipient, you are not authorized to read,
print, retain, copy, disseminate, distribute, or use this message or any part
thereof. If you receive this message in error, please notify the sender immediately
and delete all copies of this message.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
