Re: -Dmaven.test.skip=true jar:test-jar
just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true -Stephen On 3 September 2010 02:28, Andrew Hughes ahhug...@gmail.com wrote: Hi Guys, When -Dmaven.test.skip=true the jar:test-jar goals are skipped. Other modules who have a dependency on the jar:test-jar artifact then fail (unresolved dependency). Is this a sensible default for the plugin and any idea's how I can override this? Thanks heaps (again) :) --Andrew
Combined JAR / ZIP project - ZIP shouldn't fetch dependencies
Hi! I'm currently working on a packaging=jar project. In addition to the plain jar, by using the assembly plugin I also generate a jar-with-dependencies, and - using a custom assembly - a zip file (with the bin classifier). The zip file contains: * the plain jar * a batch file to run the jar * a lib directory containing the jar's dependencies The latter two parts of the artifact (the jar-with-dependencies and the zip) are both self-contained. They need nothing else to run them since all dependencies are packaged with them. When another project includes this artifact as a dependency, however, by default it tries to pull in all of the dependencies of my project too. Of course, this makes sense if they're using the plain jar. But this doesn't make sense if all they want is to consume the jar-with-dependencies or the zip file. How do I fix this? I'd like to configure it such that projects requiring just the zip/bin or jar-with-dependencies classifiers don't need to download all the dependencies. If that's not possible, another option I'd consider is NOT deploying the plain jar at all, and just deploying the jar-with-dependencies and bin, and configure it such that no-one using this artifact has to pull its dependencies. Ideas? Thanks, -- Shannon Hickey Adobe Systems Incorporated
Re: -Dmaven.test.skip=true jar:test-jar
On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: -Dmaven.test.skip=true jar:test-jar
and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Combined JAR / ZIP project - ZIP shouldn't fetch dependencies
create the zip and the jar-with-dependencies in separate modules that pull in the plain jar with scope=provided On 3 September 2010 04:36, Shannon Hickey shic...@adobe.com wrote: Hi! I'm currently working on a packaging=jar project. In addition to the plain jar, by using the assembly plugin I also generate a jar-with-dependencies, and - using a custom assembly - a zip file (with the bin classifier). The zip file contains: * the plain jar * a batch file to run the jar * a lib directory containing the jar's dependencies The latter two parts of the artifact (the jar-with-dependencies and the zip) are both self-contained. They need nothing else to run them since all dependencies are packaged with them. When another project includes this artifact as a dependency, however, by default it tries to pull in all of the dependencies of my project too. Of course, this makes sense if they're using the plain jar. But this doesn't make sense if all they want is to consume the jar-with-dependencies or the zip file. How do I fix this? I'd like to configure it such that projects requiring just the zip/bin or jar-with-dependencies classifiers don't need to download all the dependencies. If that's not possible, another option I'd consider is NOT deploying the plain jar at all, and just deploying the jar-with-dependencies and bin, and configure it such that no-one using this artifact has to pull its dependencies. Ideas? Thanks, -- Shannon Hickey Adobe Systems Incorporated
RE: Generating resource base on compilation result
It turns out that I have another plugin facing a similar problem:
I want to compile the java source first, and generate some resources
to be included in final JAR base on the compiled class.
I can only put that on or after process-classes phase. However, from
the experience stated in the original mail, adding project resources
will not work in such case.
What is the 'correct' way to put such generated resources into final
JAR?
Should I simply manually copy the result resources to
${project.build.outputDirectory}?
Is it the suggested way?
Thanks
--
Best Regards,
AdRiAN ShUM
-Original Message-
From: Adrian Shum
Sent: Wednesday, August 04, 2010 10:29 AM
To: 'Maven Users List'
Subject: RE: Generating resource base on compilation result
Hi Jesse,
Breaking out another dummy project will be my last resort, coz I also
want to make this mojo works for simple projects.
Seems the difficult if not imposssible way is my only way to go :(
Maybe what if I change my question to another way:
Is there any way to add resource to resulting jar, apart from
project.addResource() before the process-resources phase?
--
Best Regards,
AdRiAN ShUM
-Original Message-
From: Jesse Farinacci [mailto:jie...@gmail.com]
Sent: Tuesday, August 03, 2010 8:09 PM
To: Maven Users List
Subject: Re: Generating resource base on compilation result
Hi AdRiAN,
On Tue, Aug 3, 2010 at 6:53 AM, Adrian Shum tcs...@taifook.com wrote:
I am trying to develop a plugin which will generate certain resources
base on compiled classes and dependencies.
Cool.
Is there any suggestion for me?
You could quite easily solve this if you just create another module
which depends on your domain object module. Then run your classpath
scanning for @Entity / @Embedded, etc, and output a persistence.xml.
Trying to do this process in the same module without using APT *and*
using the compiled classes will be difficult if not impossible. If you
wanted to simply examine the source code and the dependency classpath,
maybe it would work. But since you're oddly requiring compiled code, I'm
fairly sure it will not.
Just break it into separate modules and all will be fine. Or use APT.
-Jesse
--
There are 10 types of people in this world, those
that can read binary and those that can not.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
This email is confidential. If you are not the intended recipient, please
delete it from your system and notify the sender immediately. Any unauthorized
use, disclosure, dissemination or copying of this email is prohibited. Taifook
Securities Group, its group companies and their content providers (Parties)
shall not be responsible for the accuracy or completeness of this email or its
attachment, if any, which could contain virus, be corrupted, destroyed,
incomplete, intercepted, lost or arrive late. The Parties do not accept
liability for any damage caused by this email.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: -Dmaven.test.skip=true jar:test-jar
Hi Guys, The problem is not that we're skipping the tests. I really don't want to run the tests... but I do want the jar:test-jar to still run and build... moduleA-0.0.0-test.jar so that other module dependencies still resolve this. On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [maven-release-plugin] Is it possible to configure maven-release-plugin to NOT pull in META-INF/LICENSE and NOTICE
Hi, I don't think it's justified for you to write to dev list. This sound like a typical user problem, not a dev one. Note a lot of developers also follow the users list, so writing to dev list is not always going to help you, if not worse. First, try answering the question that're being asked to you: what parent pom are you inheriting from? Cheers 2010/8/27 Kalle Korhonen kalle.o.korho...@gmail.com Sounds like you are using the Apache super pom as the parent. If you simply name yours LICENSE and NOTICE, they'll overwrite the default ones. Kalle On Fri, Aug 27, 2010 at 7:03 AM, Justin Edelson justinedel...@gmail.com wrote: Nothing in the release plugin will do this automatically; it must be configured somewhere, either in your POM or (more likely from the sound of it) in a parent POM. Justin On 8/27/10 5:27 AM, han hongfang wrote: Hi, Our project uses maven-release-plugin in the release process. We maintain the LICENSE.txt and NOTICE.txt (which contains module specifc statement) for each of our modules in subversion. When we issue mvn release:prepare, standard LICENSE and NOTICE files are pulled into META-INF folder of target artifact. These standard files are duplicated with LICENSE.txt and NOTICE.txt we maintained. Is it possible to configure maven-release-plugin to not pull in these files? If yes, could you show me how to do it? Thanks in advance for your reply! -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: -Dmaven.test.skip=true jar:test-jar
-DskipTests only skips running the tests not building the test-jar On 3 September 2010 09:58, Andrew Hughes ahhug...@gmail.com wrote: Hi Guys, The problem is not that we're skipping the tests. I really don't want to run the tests... but I do want the jar:test-jar to still run and build... moduleA-0.0.0-test.jar so that other module dependencies still resolve this. On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ear plugin issue
On Thu, Aug 26, 2010 at 7:36 PM, nishant@hsbcib.com wrote: Just that unable to find clientModule That's just not enough. Provide the output of mvn dependency:list and the log of your build (mvn package output.log) Stephane Nicoll stephane.nic...@gmail.com Aug 26 2010 18:35 Mail Size: 10664 Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Ear plugin issue Entity HSBC Bank plc - HBEU What error message do you get exactly? ClientModules is not a dependency of the project or something else? S. On Thu, Aug 26, 2010 at 4:20 PM, nishant@hsbcib.com wrote: It seems the attachments are not allowed. I have included the ear pom below.. ** project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion parent artifactIdProjectX/artifactId groupIdroot/groupId version1.0/version /parent groupIdroot.ProjectX/groupId artifactIdEarAssembler/artifactId version1.0/version nameEarAssembler/name packagingear/packaging build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId version2.4.2/version configuration modules jarModule groupIdroot.ProjectX/groupId artifactIdClientModules/artifactId /jarModule /modules archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration /plugin /plugins /build dependencies dependency groupIdroot.ProjectX/groupId artifactIdClientModules/artifactId version1.0/version /dependency /dependencies /project ** Thanks Nishant RAJ/HBEU/h...@hsbc Aug 26 2010 15:17 Mail Size: 8020 Please respond to Maven Users List users@maven.apache.org To users@maven.apache.org cc Subject Ear plugin issue Entity HSBC Bank plc - HBEU Hi All, I am trying to get the ear plugin working. Followed all the guidelines but could not get it working as its not able to find the module that I want to package within the ear It looks for the module in my nexus repository but does not find it. I have also got the Resolve workspace project dependencies enables in eclipse. Pom is attached. Please advice as I have been struggling with the same for few hrs now. Thanks Nishant HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ Registered in England - Number 14259 Authorised and regulated by the Financial Services Authority - SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group HSBC for the information of the addressee only and should not be reproduced and/or distributed to any other person. Each page attached hereto must be read in conjunction with any disclaimer which forms part of it. Unless otherwise stated, this transmission is neither an offer nor the solicitation of an offer to sell or purchase any investment. Its contents are based on information obtained from sources believed to be reliable but HSBC makes no representation and accepts no responsibility or liability as to its completeness or accuracy. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org HSBC Bank plc Registered Office: 8 Canada Square, London E14 5HQ Registered in England - Number 14259 Authorised and regulated by the Financial Services Authority - SAVE PAPER - THINK BEFORE YOU PRINT! This transmission has been issued by a member of the HSBC Group HSBC for the information of the
How to set the settings.xml so that the jboss-ejb3x.jar be downloaed?
I need the jboss-ejb3x-4.2.3.GA.jar. And I find it under http://repository.jboss.org/maven2;. How can I set this in the settings.xml to download this jar? I've tried set this repo as mirror/ and in repository/. But as I run mvn eclipse:eclipse it shows the mvn just connect to http://repo1.maven.org/maven2; What could be the problem? Regards -- View this message in context: http://maven.40175.n5.nabble.com/How-to-set-the-settings-xml-so-that-the-jboss-ejb3x-jar-be-downloaed-tp2802095p2802095.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
.svn/tmp directory missing or corrupt
I am trying to release a project using release:perform. When it is
checking out the project from subversion I get the error
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
I run the svn cleanup and try again but still get the same error.
I can run the svn checkout from the command line and it works fine.
Here is the output
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Online Payment System
[INFO] OPS Core Model
[INFO] OPS Web Application
[INFO] OPS Enterprise Archiva.
[INFO]
[INFO] Building Online Payment System
[INFO]task-segment: [release:perform] (aggregator-style)
[INFO]
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: svn --non-interactive checkout
svn+ssh://tmcgi...@leslie.aessuccess.org/svn/java/MavenPOC/tags/online-payment-system-1.74
checkout
[INFO] Working directory: C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT\target
[ERROR] The svn command failed.
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to checkout from SCM
Provider message:
The svn command failed.
Command output:
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 11 seconds
[INFO] Finished at: Fri Sep 03 08:36:27 EDT 2010
[INFO] Final Memory: 9M/27M
[INFO]
C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for the
above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
Re: .svn/tmp directory missing or corrupt
Hi,
It looks there is probably an issue with handling spaces in the cli.
Which version are u using of release and scm ?
Can you try with changing your -Djava.io.tmpdir= in MAVEN_OPTS env var ?
Perso, I have changed this on my windows box to something without spaces.
MAVEN_OPTS=-Xms512m -Xmx512m -Djava.io.tmpdir=/tmp/maven-tmp
2010/9/3 Timothy Mcginnis tmcgi...@aessuccess.org:
I am trying to release a project using release:perform. When it is
checking out the project from subversion I get the error
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
I run the svn cleanup and try again but still get the same error.
I can run the svn checkout from the command line and it works fine.
Here is the output
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Online Payment System
[INFO] OPS Core Model
[INFO] OPS Web Application
[INFO] OPS Enterprise Archiva.
[INFO]
[INFO] Building Online Payment System
[INFO] task-segment: [release:perform] (aggregator-style)
[INFO]
[INFO] [release:perform {execution: default-cli}]
[INFO] Checking out the project to perform the release ...
[INFO] Executing: svn --non-interactive checkout
svn+ssh://tmcgi...@leslie.aessuccess.org/svn/java/MavenPOC/tags/online-payment-system-1.74
checkout
[INFO] Working directory: C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT\target
[ERROR] The svn command failed.
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Unable to checkout from SCM
Provider message:
The svn command failed.
Command output:
svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup'
and try again
svn: Can't open file
'checkout\online-payment-system-core\src\main\java\com\aes\ops\configuration\.svn\tmp\text-base\GetEnvironmentIndependentConfigurationServicePojo.java.svn-base':
The system cannot find the path specified.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 11 seconds
[INFO] Finished at: Fri Sep 03 08:36:27 EDT 2010
[INFO] Final Memory: 9M/27M
[INFO]
C:\Documents and
Settings\tmcginni\IBM\rationalsdp7.0\svnPOC\online-payment-system-1.74-SNAPSHOT
Tim McGinnis
717 720-1962
Web Development
AES/PHEAA
==
This message contains privileged and confidential information intended for
the above addressees only. If you
receive this message in error please delete or destroy this message and/or
attachments.
The sender of this message will fully cooperate in the civil and criminal
prosecution of any individual engaging
in the unauthorized use of this message.
==
--
Olivier
http://twitter.com/olamy
http://fr.linkedin.com/in/olamy
http://www.viadeo.com/fr/profile/olivier.lamy7
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to set the settings.xml so that the jboss-ejb3x.jar be downloaed?
This problem is solved. Please don't answer -- View this message in context: http://maven.40175.n5.nabble.com/How-to-set-the-settings-xml-so-that-the-jboss-ejb3x-jar-be-downloaed-tp2802095p2802182.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: -Dmaven.test.skip=true jar:test-jar
There are a number of pitfalls with test jars. My entirely personal suggestion is this: any time you are tempted to put a test jar configuration into a POM, just go and make a new, ordinary, project with the shared test code in it, and use it with scopetest/scope. You won't regret it. On Fri, Sep 3, 2010 at 5:26 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: -DskipTests only skips running the tests not building the test-jar On 3 September 2010 09:58, Andrew Hughes ahhug...@gmail.com wrote: Hi Guys, The problem is not that we're skipping the tests. I really don't want to run the tests... but I do want the jar:test-jar to still run and build... moduleA-0.0.0-test.jar so that other module dependencies still resolve this. On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: -Dmaven.test.skip=true jar:test-jar
That is my personal preference as well, but sometimes people do what they want to do ;-) On 3 September 2010 15:14, Benson Margulies bimargul...@gmail.com wrote: There are a number of pitfalls with test jars. My entirely personal suggestion is this: any time you are tempted to put a test jar configuration into a POM, just go and make a new, ordinary, project with the shared test code in it, and use it with scopetest/scope. You won't regret it. On Fri, Sep 3, 2010 at 5:26 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: -DskipTests only skips running the tests not building the test-jar On 3 September 2010 09:58, Andrew Hughes ahhug...@gmail.com wrote: Hi Guys, The problem is not that we're skipping the tests. I really don't want to run the tests... but I do want the jar:test-jar to still run and build... moduleA-0.0.0-test.jar so that other module dependencies still resolve this. On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Integrating externally run Junit test reports back into maven
All, [I've done a quick search and haven't seen anything, so I'm hoping someone can point me in the right direction.] I have a need to run some integration tests externally to Maven (under a continuous integration environment) . That is, physically run the tests (and the system under test) on separate machines (without maven support, for now). I've gotten things to the point where I can get the maven POM to remote deploy and execute the tests under junit (during the integration-test phase). Now, effectively, what I'd like to do is get the (remote) junit test reports/status and merge that back into the maven process (presumably during the verify phase) back in the CI. My setup, is similar to the following psuedo-POM: [snip] plugin artifactIdmaven-antrun-plugin/artifactId version1.4/version executions execution phase integration-test /phase configuration tasks !-- execute script that: - deploys project's artifacts to remote hosts - runs junit on project's integration tests and generates reports - copies junit's reports back onto local system (e.g. target/failsafe-reports) /exec /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin plugin groupIdorg.codehaus.mojo/groupId artifactIdfailsafe-maven-plugin/artifactId version2.4.3/version executions execution goals goalverify/goal /goals /execution /executions /plugin [snip] Right now, the above setup fails with: ...target/failsafe-reports/failsafe-summary.xml (No such file or directory) I'm hoping someone on the list has already blazed this trail, which would save me from searching through the failsafe/surefire plugin codebase. [The test systems aren't under my direct control don't have maven installed there.] Regards, Bob - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
New Site plugin configuration fails if example config from wiki is used?
Using maven 3.0-beta-3 and the maven-site-plugin 3.0-beta-2-SNAPSHOT and specifying the reportPlugins configuration as shown on https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html I get the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site fo r parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:157) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:535) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:96) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) ... 19 more Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.init(ComponentValueSetter.java:80) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:89) at org.codehaus.plexus.component.configurator.converters.composite.ArrayConverter.fromConfiguration(ArrayConverter.java:131) at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:260) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:505) ... 22 more [ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read
Re: New Site plugin configuration fails if example config from wiki is used?
I haven't tried maven 3.0-beta-3 with the site plugin yet, but based on the conversations I've read (on the dev list) maven-site-plugin 3.0-beta-2-SNAPSHOT should be updated to work. The release process for maven-site-plugin 3.0-beta-2 is supposed to start shortly, so I advice you to monitor the dev list and provide any feedback you have! /Anders On Fri, Sep 3, 2010 at 17:29, Raphael Ackermann rtac...@gmail.com wrote: Using maven 3.0-beta-3 and the maven-site-plugin 3.0-beta-2-SNAPSHOT and specifying the reportPlugins configuration as shown on https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html I get the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site fo r parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:157) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:535) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:96) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) ... 19 more Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.init(ComponentValueSetter.java:80) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:89) at org.codehaus.plexus.component.configurator.converters.composite.ArrayConverter.fromConfiguration(ArrayConverter.java:131) at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:260) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
Re: New Site plugin configuration fails if example config from wiki is used?
Hi, Thanks for reporting this. It's now fixed and I have deployed a new SNAPSHOT. 2010/9/3 Raphael Ackermann rtac...@gmail.com: Using maven 3.0-beta-3 and the maven-site-plugin 3.0-beta-2-SNAPSHOT and specifying the reportPlugins configuration as shown on https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html I get the following error: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site (default-site) on project usp-sls-appliance: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site fo r parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:157) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:88) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:80) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:87) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:315) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168) at org.apache.maven.cli.MavenCli.main(MavenCli.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable to parse configuration of mojo org.apache.maven.plugins:maven-site-plugin:3.0-beta-2-SNAPSHOT:site for parameter plugin: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:535) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:467) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:96) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) ... 19 more Caused by: org.codehaus.plexus.component.configurator.ComponentConfigurationException: Cannot find setter nor field in org.apache.maven.plugins.site.ReportPlugin for 'reports' at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.init(ComponentValueSetter.java:80) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:89) at org.codehaus.plexus.component.configurator.converters.composite.ArrayConverter.fromConfiguration(ArrayConverter.java:131) at org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:260) at org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137) at org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56) at org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:505)
Release Plugin Failing on Commit
I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: [INFO] Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Path 'svn://SVN IP/data/svn/client/myapp/tags/myapp-1.1.rc4' does not exist in revision 5218 To be fair, that's true--myapp-1.1.rc4 isn't a folder in the SVN tags folder. But I figured the plugin would create it and put my source code underneath. Another weird thing is that the poms are updated to 1.1.rc4 and committed to the trunk and checked out to my local machine. The expected behavior is for 1.1.rc5-SNAPSHOT to be in the trunk and on my local while the 1.1.rc4 is in the tagged version. Here is the plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration updateWorkingCopyVersionsfalse/updateWorkingCopyVersions preparationGoalsclean install/preparationGoals goalsclean install/goals arguments-Dmaven.test.skip/arguments tagBasesvn://SVN IP/data/svn/client/myapp/tags /tagBase autoVersionSubmodulestrue/autoVersionSubmodules /configuration /plugin Any advice on how to get the expected behavior is appreciated. Thanks.
Re: Release Plugin Failing on Commit
On Fri, Sep 3, 2010 at 6:16 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I am using version 2.0 of the release plugin to tag a new version of my multi-module application, but at the end when it goes to commit to SVN SCM, I get the following: What command did you execute? What does the scm section of the pom look like? Also, it looks like there is a trailing space in your tagBase element, which might be causing trouble. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: -Dmaven.test.skip=true jar:test-jar
I was avoiding this, but you're both only re-enforcing what I was thinking of doing. I have raised this as an issue (improvement) for the jar plugin http://jira.codehaus.org/browse/MJAR-138 at least it's on the radar that way. Please feel encouraged to comment/edit the issue if you can add improve or compliment any of the info I submitted. Thanks v much for your help CHEERS :) On Fri, Sep 3, 2010 at 11:48 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That is my personal preference as well, but sometimes people do what they want to do ;-) On 3 September 2010 15:14, Benson Margulies bimargul...@gmail.com wrote: There are a number of pitfalls with test jars. My entirely personal suggestion is this: any time you are tempted to put a test jar configuration into a POM, just go and make a new, ordinary, project with the shared test code in it, and use it with scopetest/scope. You won't regret it. On Fri, Sep 3, 2010 at 5:26 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: -DskipTests only skips running the tests not building the test-jar On 3 September 2010 09:58, Andrew Hughes ahhug...@gmail.com wrote: Hi Guys, The problem is not that we're skipping the tests. I really don't want to run the tests... but I do want the jar:test-jar to still run and build... moduleA-0.0.0-test.jar so that other module dependencies still resolve this. On Fri, Sep 3, 2010 at 5:08 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: and you don't need the =true for -DskipTests On 3 September 2010 08:17, Barrie Treloar baerr...@gmail.com wrote: On Fri, Sep 3, 2010 at 4:15 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: just use -DskipTests as that will skip running the tests but not compiling or packaging them... oh and it's shorter than its alias -Dmaven.skip.test.exec=true as well as the bigger skip that you are using -Dmaven.skip.test=true Whoops. If I had read our internal wiki with this help hints I would have read: Skip Running Tests Run maven with -DskipTests=true, e.g.: mvn install -DskipTests=true (Dont use maven.test.skip as this doesn't generate the test-jar) Apologies. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
