post-integration-test must be executed
Hello, We're doing some integration tests with bash scripts, and these are executed with Maven's exec plugin. When the test works, it returns 0, when it fails, it returns 1. When it returns 1, the exec plugin will fail and the post-integration-test goal will not be executed. It is crucial for it to be executed to clean up the environment. I saw this issue came up 3 years ago at http://jira.codehaus.org/browse/MNG-2142 but the fix is available only for Maven version 3? Is there a way to force the execution of post-integration-test even if the integration-test fails? Or I have to write my own plugin? Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: post-integration-test must be executed
wrap your bash scripts in a bash script that checks the exit code and creates a file based on the exit code. then attach an execution to the verify phase that checks your file. Essentially, the rule for integration-test is to _never_ fail the build... hence: failsafe-maven-plugin as an alternative to surefire... it splits the test execution from the test result checking to ensure that the post-integration-test phase always runs -Stephen 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, We're doing some integration tests with bash scripts, and these are executed with Maven's exec plugin. When the test works, it returns 0, when it fails, it returns 1. When it returns 1, the exec plugin will fail and the post-integration-test goal will not be executed. It is crucial for it to be executed to clean up the environment. I saw this issue came up 3 years ago at http://jira.codehaus.org/browse/MNG-2142 but the fix is available only for Maven version 3? Is there a way to force the execution of post-integration-test even if the integration-test fails? Or I have to write my own plugin? Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: post-integration-test must be executed
The problem is Surefire and, as far as I can see, this failsafe plugin, are made for Java unit tests, while in our case we test C++ applications. As far as Maven is concerned, we just execute a script with exec plugin, which returns 0 or 1, and if it returns 1, then the deploy should fail, BUT NOT the post-integration-test. So the solution would probably be to write our own plugin which does the hack you mentioned? Stephen Connolly wrote: wrap your bash scripts in a bash script that checks the exit code and creates a file based on the exit code. then attach an execution to the verify phase that checks your file. Essentially, the rule for integration-test is to _never_ fail the build... hence: failsafe-maven-plugin as an alternative to surefire... it splits the test execution from the test result checking to ensure that the post-integration-test phase always runs -Stephen 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, We're doing some integration tests with bash scripts, and these are executed with Maven's exec plugin. When the test works, it returns 0, when it fails, it returns 1. When it returns 1, the exec plugin will fail and the post-integration-test goal will not be executed. It is crucial for it to be executed to clean up the environment. I saw this issue came up 3 years ago at http://jira.codehaus.org/browse/MNG-2142 but the fix is available only for Maven version 3? Is there a way to force the execution of post-integration-test even if the integration-test fails? Or I have to write my own plugin? Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Building sub projects pom from parent's pom.
Thanks. It was helpful. Is there any way to make projA as war. Thanks, Pinky Muralidhar. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Monday, November 23, 2009 12:24 PM To: Maven Users List Subject: Re: Building sub projects pom from parent's pom. projA should not be a war project, it should merely be a aggregation pom. Move your war project to a sub-project. Read this: http://www.sonatype.com/books/maven-book/reference/multimodule.html /Anders On Mon, Nov 23, 2009 at 07:45, pinky.muralid...@wipro.com wrote: Hi, I am new to maven. Anyways I was able to build my war using maven build. I wanted to move forward from where I need to call other dependent sub project's maven.cmd first from my pom.xml. My project structure looks like this : projA | |-subProjA | |-pom.xml | |- maven.cmd | |-subProjB | |-pom.xml | |- maven.cmd | |-subProjC | |-pom.xml | |- maven.cmd | |-pom.xml |- maven.cmd projA's pom.xml must be able to call all subProj's maven.cmd before building the projA.war. Please guide me. Thanks in Advance, Pinky Muralidhar. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: post-integration-test must be executed
or use two executions of exec, or an execution of exec and antrun, or write your own plugin 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: The problem is Surefire and, as far as I can see, this failsafe plugin, are made for Java unit tests, while in our case we test C++ applications. As far as Maven is concerned, we just execute a script with exec plugin, which returns 0 or 1, and if it returns 1, then the deploy should fail, BUT NOT the post-integration-test. So the solution would probably be to write our own plugin which does the hack you mentioned? Stephen Connolly wrote: wrap your bash scripts in a bash script that checks the exit code and creates a file based on the exit code. then attach an execution to the verify phase that checks your file. Essentially, the rule for integration-test is to _never_ fail the build... hence: failsafe-maven-plugin as an alternative to surefire... it splits the test execution from the test result checking to ensure that the post-integration-test phase always runs -Stephen 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, We're doing some integration tests with bash scripts, and these are executed with Maven's exec plugin. When the test works, it returns 0, when it fails, it returns 1. When it returns 1, the exec plugin will fail and the post-integration-test goal will not be executed. It is crucial for it to be executed to clean up the environment. I saw this issue came up 3 years ago at http://jira.codehaus.org/browse/MNG-2142 but the fix is available only for Maven version 3? Is there a way to force the execution of post-integration-test even if the integration-test fails? Or I have to write my own plugin? Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to copy jar (also) to target installation dir
Maven says that antrun copy corresponds to maven-resource-plugin, (from http://maven.apache.org/plugins/maven-antrun-plugin/usage.html). Can i use the maven-resources-plugin instead? i'm already using it to copy conf cron files: plugin artifactIdmaven-resources-plugin/artifactId version2.4.1/version executions execution idcopy-conf/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/ct-urlf-increase-priority//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.properties/include /includes /resource /resources /configuration /execution execution i just thought it's not intended to copy jars also resources... Eyal. On Sun, Nov 22, 2009 at 4:21 PM, Sony Antony sony.ant...@gmail.com wrote: It should work with the antrun plugin ( and ant's copy task. ) ( configure an antrun plugin execution to attach to install phase ) --sony On Sun, Nov 22, 2009 at 8:43 AM, eyal edri eyal.e...@gmail.com wrote: I want to config the pom project to copy the final jar file to an installation dir and bind it to the 'install' phase. meaning, when i just build the project, the jar will be built into the default target/project.jar. but when i install it should be also should be copied to /usr/local/application/project.jar. i tried adding OutputDirectory in the 'jar' plugin, but it just changed the default target. -- Eyal Edri -- Eyal Edri
Re: Building sub projects pom from parent's pom.
Hmm, possibly. But that's not the Maven way. So don't go there! /Anders On Mon, Nov 23, 2009 at 11:21, pinky.muralid...@wipro.com wrote: Thanks. It was helpful. Is there any way to make projA as war. Thanks, Pinky Muralidhar. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Monday, November 23, 2009 12:24 PM To: Maven Users List Subject: Re: Building sub projects pom from parent's pom. projA should not be a war project, it should merely be a aggregation pom. Move your war project to a sub-project. Read this: http://www.sonatype.com/books/maven-book/reference/multimodule.html /Anders On Mon, Nov 23, 2009 at 07:45, pinky.muralid...@wipro.com wrote: Hi, I am new to maven. Anyways I was able to build my war using maven build. I wanted to move forward from where I need to call other dependent sub project's maven.cmd first from my pom.xml. My project structure looks like this : projA | |-subProjA | |-pom.xml | |- maven.cmd | |-subProjB | |-pom.xml | |- maven.cmd | |-subProjC | |-pom.xml | |- maven.cmd | |-pom.xml |- maven.cmd projA's pom.xml must be able to call all subProj's maven.cmd before building the projA.war. Please guide me. Thanks in Advance, Pinky Muralidhar. Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: how to copy jar (also) to target installation dir
technically, yes... but you'll be fighting with the standard bindings. what you are trying to do is not the maven way so your best bet is to just use antrun and copy 2009/11/23 eyal edri eyal.e...@gmail.com: Maven says that antrun copy corresponds to maven-resource-plugin, (from http://maven.apache.org/plugins/maven-antrun-plugin/usage.html). Can i use the maven-resources-plugin instead? i'm already using it to copy conf cron files: plugin artifactIdmaven-resources-plugin/artifactId version2.4.1/version executions execution idcopy-conf/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/ct-urlf-increase-priority//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.properties/include /includes /resource /resources /configuration /execution execution i just thought it's not intended to copy jars also resources... Eyal. On Sun, Nov 22, 2009 at 4:21 PM, Sony Antony sony.ant...@gmail.com wrote: It should work with the antrun plugin ( and ant's copy task. ) ( configure an antrun plugin execution to attach to install phase ) --sony On Sun, Nov 22, 2009 at 8:43 AM, eyal edri eyal.e...@gmail.com wrote: I want to config the pom project to copy the final jar file to an installation dir and bind it to the 'install' phase. meaning, when i just build the project, the jar will be built into the default target/project.jar. but when i install it should be also should be copied to /usr/local/application/project.jar. i tried adding OutputDirectory in the 'jar' plugin, but it just changed the default target. -- Eyal Edri -- Eyal Edri - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RPM dependencies
Hello, We would like to use RPMs similarly to JARs. This means that, when we install a project, its rpm would go into the repository. When another project is using this project, then the rpm should be fetched from the repository and installed. Is there a good way to do this? The problem might also be that we need to install the rpms in su mode, though this can be solved for now by running sudo mvn All ideas are welcome! Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
phase war:war-Copying webapp resources overwrites already processed resources
I'm trying to compress javascript files inside webapp directory (using yuicompressor) . Those compressed files are saved into target directory. In the packaging phase war:war are those compressed files overwriten by their uncompressed originals. This happens in the Copying webapp resources action. Is there any way to prevent overwriting webapp resources that are already in target directory? I'm using Maven2. There was a property in Maven1 called: maven.war.resources.overwrite. This is not working anymore. I've also tried to start compression in different phase such as prepare-package. But this doesn't help, because i would need to inject compression between Copying webapp resources and Building war. See this log for better imagination: [war:war] [INFO] Packaging webapp [INFO] Assembling webapp[MYAPP] in [/data/pub/deploy/MYAPP/target/MYAPP] [INFO] Processing war project [INFO] Copying webapp resources[/data/pub/deploy/MYAPP/src/main/webapp] --- inject compression HERE [INFO] Building war: /data/pub/deploy/MYAPP/target/MYAPP.war Please, does anyone know how to solve this problem in correct manner? David Benes
Re: Activating a profile based on the deactivation of other profiles
Hi Wendy, Thanks a lot, that worked well, when I finally got around to trying it out! Ricky. 2009/10/28 Wendy Smoak wsm...@gmail.com: On Wed, Oct 28, 2009 at 5:11 AM, Ricky Clarkson ricky.clark...@gmail.com wrote: So my question is; how can I make it so that development-brand is activated only if none of the other brands are? You're on the right track by activating the default profile on the *absence* of a property with the !. Now, stop using -P to activate the other profiles, and switch to using -D=[value]. You'll need to add similar activation sections to the other branded ones. Then you can activate exactly one profile with -Dbrand=... (or nothing, for the default). -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ricky Clarkson Java and Scala Programmer, AD Holdings +44 1565 770804 Skype: ricky_clarkson Google Talk: ricky.clark...@gmail.com Google Wave: ricky.clark...@googlewave.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RPM dependencies
you can try playing with the rpm plugin from mojo: http://mojo.codehaus.org/rpm-maven-plugin/ i'm actually in the same boat as you are. we've been programming in perl till now, using rpm yum for deployment. but from what i learned so far about Maven, you might find that it can replace any functionality you got from rpm/yum, thus rendering the use of rpm packaging redundant. Eyal. 2009/11/23 Gajo Csaba csaba.g...@cosylab.com Hello, We would like to use RPMs similarly to JARs. This means that, when we install a project, its rpm would go into the repository. When another project is using this project, then the rpm should be fetched from the repository and installed. Is there a good way to do this? The problem might also be that we need to install the rpms in su mode, though this can be solved for now by running sudo mvn All ideas are welcome! Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Eyal Edri
Re: RPM dependencies
I have been actually using the rpm plugin, found a few bugs in it etc... The problem is, when you install C++ projects, you want some .h files to be copied to /usr/include, some .so files to /usr/lib etc. so it cannot work as easily as for Java projects. I'm guessing it's easy for Perl as well, since you've got packages... eyal edri wrote: you can try playing with the rpm plugin from mojo: http://mojo.codehaus.org/rpm-maven-plugin/ i'm actually in the same boat as you are. we've been programming in perl till now, using rpm yum for deployment. but from what i learned so far about Maven, you might find that it can replace any functionality you got from rpm/yum, thus rendering the use of rpm packaging redundant. Eyal. 2009/11/23 Gajo Csaba csaba.g...@cosylab.com Hello, We would like to use RPMs similarly to JARs. This means that, when we install a project, its rpm would go into the repository. When another project is using this project, then the rpm should be fetched from the repository and installed. Is there a good way to do this? The problem might also be that we need to install the rpms in su mode, though this can be solved for now by running sudo mvn All ideas are welcome! Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RPM dependencies
i found that the rpm plugin only worked with maven 2.0.6 - 2.0.10. i found a solution for coping file using the resouces:copy-resoucres plugin or use the assembly pluging to create a dist pkg of .tar.gz. here's a 'build' for pom.xml i've created: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/lib/ctch/java/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin plugin artifactIdmaven-resources-plugin/artifactId version2.4.1/version executions execution idcopy-conf/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/ct-urlf-increase-priority//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.properties/include /includes /resource /resources /configuration /execution execution idcopy-cron/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/cron.d//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.cron/include /includes /resource /resources /configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration outputDirectory/usr/local/ct-urlf-increase-priority/outputDirectory archive manifest mainClasscom.commtouch.url.unknowns.IncreasePriority/mainClass addClasspathtrue/addClasspath classpathPrefix/usr/lib/ctch/java/classpathPrefix /manifest /archive /configuration /plugin /plugins /build On Mon, Nov 23, 2009 at 3:47 PM, Gajo Csaba csaba.g...@cosylab.com wrote: I have been actually using the rpm plugin, found a few bugs in it etc... The problem is, when you install C++ projects, you want some .h files to be copied to /usr/include, some .so files to /usr/lib etc. so it cannot work as easily as for Java projects. I'm guessing it's easy for Perl as well, since you've got packages... eyal edri wrote: you can try playing with the rpm plugin from mojo: http://mojo.codehaus.org/rpm-maven-plugin/ i'm actually in the same boat as you are. we've been programming in perl till now, using rpm yum for deployment. but from what i learned so far about Maven, you might find that it can replace any functionality you got from rpm/yum, thus rendering the use of rpm packaging redundant. Eyal. 2009/11/23 Gajo Csaba csaba.g...@cosylab.com Hello, We would like to use RPMs similarly to JARs. This means that, when we install a project, its rpm would go into the repository. When another project is using this project, then the rpm should be fetched from the repository and installed. Is there a good way to do this? The problem might also be that we need to install the rpms in su mode, though this can be solved for now by running sudo mvn All ideas are welcome! Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Eyal Edri
versioning using properties
As a lot of other maven users (I have read many threads on this topic), I try to limit the places where version numbers are explicitely set. I have uploaded http://rapidshare.de/files/48725253/test-mvn.zip.html here a small test case to illustrate what i say below. My multiproject P1 holds a single module A. P1 pom declares a property P1.version, which is used to set the artifact version of P1, the artifact version of A, the parent version of A. I can build P1, as A finds its parent from the file system. I can no longer build A alone, but I accomodate with that. A project P0 uses A. P0 declares the P1.version property, and declares A as a dependency. I cannot build P0, as A cannot find its parent. It seems that the P1.version definition from P0 is not known or interpreted when maven resolves the parent section of A. Of course, if P0 and P1 are defined as modules of a super project, then I can build the super project. Is there any rationale for this behaviour ? Thanks for your comments. -- View this message in context: http://old.nabble.com/versioning-using-properties-tp26478836p26478836.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: RPM dependencies
I see, you're copying all resources to the include etc. dirs when you write mvn install. I guess I would need something similar (I'll have to confirm). I was actually thinking of fetching rpms in the first phase (copy-resources?), before compiling. Then I'd try to install the rpm, if it's already installed then just skip it, and then do the compile (by calling make). Thanks for the idea! eyal edri wrote: i found that the rpm plugin only worked with maven 2.0.6 - 2.0.10. i found a solution for coping file using the resouces:copy-resoucres plugin or use the assembly pluging to create a dist pkg of .tar.gz. here's a 'build' for pom.xml i've created: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId executions execution idcopy-dependencies/id phasepackage/phase goals goalcopy-dependencies/goal /goals configuration outputDirectory/usr/lib/ctch/java/outputDirectory overWriteReleasesfalse/overWriteReleases overWriteSnapshotsfalse/overWriteSnapshots overWriteIfNewertrue/overWriteIfNewer /configuration /execution /executions /plugin plugin artifactIdmaven-resources-plugin/artifactId version2.4.1/version executions execution idcopy-conf/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/ct-urlf-increase-priority//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.properties/include /includes /resource /resources /configuration /execution execution idcopy-cron/id phaseinstall/phase goals goalcopy-resources/goal /goals configuration outputDirectory/etc/cron.d//outputDirectory resources resource directorysrc/main/resources/directory filteringtrue/filtering includes include**/*.cron/include /includes /resource /resources /configuration /execution /executions /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration outputDirectory/usr/local/ct-urlf-increase-priority/outputDirectory archive manifest mainClasscom.commtouch.url.unknowns.IncreasePriority/mainClass addClasspathtrue/addClasspath classpathPrefix/usr/lib/ctch/java/classpathPrefix /manifest /archive /configuration /plugin /plugins /build On Mon, Nov 23, 2009 at 3:47 PM, Gajo Csaba csaba.g...@cosylab.com wrote: I have been actually using the rpm plugin, found a few bugs in it etc... The problem is, when you install C++ projects, you want some .h files to be copied to /usr/include, some .so files to /usr/lib etc. so it cannot work as easily as for Java projects. I'm guessing it's easy for Perl as well, since you've got packages... eyal edri wrote: you can try playing with the rpm plugin from mojo: http://mojo.codehaus.org/rpm-maven-plugin/ i'm actually in the same boat as you are. we've been programming in perl till now, using rpm yum for deployment. but from what i learned so far about Maven, you might find that it can replace any functionality you got from rpm/yum, thus rendering the use of rpm packaging redundant. Eyal. 2009/11/23 Gajo Csaba csaba.g...@cosylab.com Hello, We would like to use RPMs similarly to JARs. This means that, when we install a project, its rpm would go into the repository. When another project is using this project, then the rpm should be fetched from the repository and installed. Is there a good way to do this? The problem might also be that we need to install the rpms in su mode, though this can be solved for now by running sudo mvn All ideas are welcome! Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- _ _ _ _ _ |_| |_| |_| |_| |_|
Thoughts on build vs deploy time property filtering
Hi, I was hoping for some thoughts from the community about the reasons behind why one might want to filter at build time versus at deploy time. Traditionally, our organization built one artifact from version control that still contained property placeholders. We would filter those artifacts at deploy time, so that the artifact was completed as it deployed to the target environment. This was seen as beneficial as we only had to build our artifact once, and then we can deploy that same artifact multiple times. It appears as though maven prefers to filter at build time, and create a different artifact per environment. What are the benefits of this methodology? It looks like you would have to do multiple builds (to produce an environment-specific artifact), where before, we could only build a filterable artifact once. Thanks
Re: phase war:war-Copying webapp resources overwrites already processed resources
Is there any way to prevent overwriting webapp resources that are already in target directory? Are you using any filtering while processing your resources, or no? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Skip dependencies
Hello, Is there a way to write a plugin or something, which would check if a dependency exists, and if it doesn't, then just skips it? Currently if a dependency is missing and cannot be downloaded, then the build will fail. Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] [FR] Apache Maven, enfin un livre en Français
Hi community, This mail is to announce the availability of a new book about Maven, but in French this time ! Thus let's talk in French, non-french readers can mute this thread :-) Bonjour à tous, Petit mail pour vous prévenir de la disponibilité d'un nouvel ouvrage en Français sur votre produit préféré : Maven. Il s'agit d'un ouvrage original qui a pour but de vous livrer un concentré d'expérience autour de cet outil que Nicolas De loof et moi-même avons acquis en plus de 6 ans de pratique. Nous avons essayé d'être inventif en créant un nouveau style littéraire : Le roman informatique. On vous laisse découvrir tout cela en espérant que vous y appreniez beaucoup de choses et que les 300 pages de Français vous seront plus accessibles. La préface est rédigée par Jason Van Zyl (pas la peine que je vous rappelle de qui il s'agit ?? ;-) ) Plus de détails et actualités sur cet ouvrage sur mon blog ( http://blog.aheritier.net/apache-maven-enfin-un-livre-en-francais/), celui de Nicolas (http://blog.loof.fr/) et sur le site de l'éditeur ( http://www.pearson.fr/livre/?GCOI=27440100730370). Cordialement, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net
Re: Skip dependencies
Hi, I think thats the point of the dependency, to be there, why do you use a dependency in your pom when it's not necesarry? :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, Is there a way to write a plugin or something, which would check if a dependency exists, and if it doesn't, then just skips it? Currently if a dependency is missing and cannot be downloaded, then the build will fail. Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip dependencies
Hello Csaba :) The problem I might potentially have is that we use two repositories, one is Maven and the other is YUM. So it is possible for an artifact (rpm) to be in YUM, but not in the Maven repository. In this case, my plugin would check if it's in YUM and download it... otherwise it would fail. But it should not fail if it's not in the Maven repository. Regards, Csaba Csaba Madai wrote: Hi, I think thats the point of the dependency, to be there, why do you use a dependency in your pom when it's not necesarry? :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, Is there a way to write a plugin or something, which would check if a dependency exists, and if it doesn't, then just skips it? Currently if a dependency is missing and cannot be downloaded, then the build will fail. Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip dependencies
Have you tried Artifactory? It's not a plugin, but I assume it will do the job for you :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello Csaba :) The problem I might potentially have is that we use two repositories, one is Maven and the other is YUM. So it is possible for an artifact (rpm) to be in YUM, but not in the Maven repository. In this case, my plugin would check if it's in YUM and download it... otherwise it would fail. But it should not fail if it's not in the Maven repository. Regards, Csaba Csaba Madai wrote: Hi, I think thats the point of the dependency, to be there, why do you use a dependency in your pom when it's not necesarry? :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, Is there a way to write a plugin or something, which would check if a dependency exists, and if it doesn't, then just skips it? Currently if a dependency is missing and cannot be downloaded, then the build will fail. Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skip dependencies
Ah cool, some of my colleagues are experimenting with it, I'll ask them tomorrow! Csaba Madai wrote: Have you tried Artifactory? It's not a plugin, but I assume it will do the job for you :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello Csaba :) The problem I might potentially have is that we use two repositories, one is Maven and the other is YUM. So it is possible for an artifact (rpm) to be in YUM, but not in the Maven repository. In this case, my plugin would check if it's in YUM and download it... otherwise it would fail. But it should not fail if it's not in the Maven repository. Regards, Csaba Csaba Madai wrote: Hi, I think thats the point of the dependency, to be there, why do you use a dependency in your pom when it's not necesarry? :) Csaba 2009/11/23 Gajo Csaba csaba.g...@cosylab.com: Hello, Is there a way to write a plugin or something, which would check if a dependency exists, and if it doesn't, then just skips it? Currently if a dependency is missing and cannot be downloaded, then the build will fail. Thanks, Csaba - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
JAX-WS Hello World Example
After searching all over the web to try and find this answer, does anyone seem to know about a working JAX-WS example built using Maven? I have found a couple that purport to be tutorials but couldn't get a single one to build. Anyway, the best one I have found thus far was: http://www.omii.ac.uk/wiki/JaxWsTutorial But it detonates when I try and run mvn install. If anyone out there could help get this to work or give me some guidance on how to create the examples I would package the client and server examples and post it for others's benefit as well. Thanks, Andy -- View this message in context: http://old.nabble.com/JAX-WS-Hello-World-Example-tp26484077p26484077.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: JAX-WS Hello World Example
CXF incorporates several. On Mon, Nov 23, 2009 at 2:08 PM, nhcoder andrewnbenja...@hotmail.comwrote: After searching all over the web to try and find this answer, does anyone seem to know about a working JAX-WS example built using Maven? I have found a couple that purport to be tutorials but couldn't get a single one to build. Anyway, the best one I have found thus far was: http://www.omii.ac.uk/wiki/JaxWsTutorial But it detonates when I try and run mvn install. If anyone out there could help get this to work or give me some guidance on how to create the examples I would package the client and server examples and post it for others's benefit as well. Thanks, Andy -- View this message in context: http://old.nabble.com/JAX-WS-Hello-World-Example-tp26484077p26484077.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: Thoughts on build vs deploy time property filtering
Well, I would argue that you should keep all environment specific configuration outside of your artifact. How can you do filtering on deploy? Do you explode your jar/war/ear, filter, and then repack? /Anders On Mon, Nov 23, 2009 at 16:59, John Prystash stash1...@yahoo.com wrote: Hi, I was hoping for some thoughts from the community about the reasons behind why one might want to filter at build time versus at deploy time. Traditionally, our organization built one artifact from version control that still contained property placeholders. We would filter those artifacts at deploy time, so that the artifact was completed as it deployed to the target environment. This was seen as beneficial as we only had to build our artifact once, and then we can deploy that same artifact multiple times. It appears as though maven prefers to filter at build time, and create a different artifact per environment. What are the benefits of this methodology? It looks like you would have to do multiple builds (to produce an environment-specific artifact), where before, we could only build a filterable artifact once. Thanks
Re: The integration-test phase meaning?
Hey Brettporter, could i have this slide as well?! thanks brettporter wrote: You're correct, though realistically a number of projects go for a separate project for this type of testing. I'm currently preparing some slides on this for my talk at ApacheCon - they should be posted after the conference. If anyone has any particular testing practices they want to see covered, let me know :) Cheers, Brett 2008/10/14 陈思淼 chensim...@gmail.com If the Project contains lots of subproject and the final project result is a Big EAR package. I think the integration-test is to put the ear package into jboss or other app server to do the test thing lots of environment variable for example: database connection parameter, the domain url, the SOA service url are different with the unit test. but the integration-test is hard to perform because of the environment difficult. I can see the maven-war-plugin have the war:run mojo binding with the integration-test , Is there any best practice who can make smooth and productive integration-test in their project, can you share with me ? -- Brett Porter http://blogs.exist.com/bporter/ -- View this message in context: http://n2.nabble.com/The-integration-test-phase-meaning-tp1331698p4054041.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: [ANN] [FR] Apache Maven, enfin un livre en Fran çais
A big +1 Bravo Arnaud et Nicolas ! Le 23 novembre 2009 18:02, Arnaud HERITIER arnaud.herit...@exoplatform.com a écrit : Hi community, This mail is to announce the availability of a new book about Maven, but in French this time ! Thus let's talk in French, non-french readers can mute this thread :-) Bonjour à tous, Petit mail pour vous prévenir de la disponibilité d'un nouvel ouvrage en Français sur votre produit préféré : Maven. Il s'agit d'un ouvrage original qui a pour but de vous livrer un concentré d'expérience autour de cet outil que Nicolas De loof et moi-même avons acquis en plus de 6 ans de pratique. Nous avons essayé d'être inventif en créant un nouveau style littéraire : Le roman informatique. On vous laisse découvrir tout cela en espérant que vous y appreniez beaucoup de choses et que les 300 pages de Français vous seront plus accessibles. La préface est rédigée par Jason Van Zyl (pas la peine que je vous rappelle de qui il s'agit ?? ;-) ) Plus de détails et actualités sur cet ouvrage sur mon blog ( http://blog.aheritier.net/apache-maven-enfin-un-livre-en-francais/), celui de Nicolas (http://blog.loof.fr/) et sur le site de l'éditeur ( http://www.pearson.fr/livre/?GCOI=27440100730370). Cordialement, Arnaud Héritier Software Factory Manager eXo platform - http://www.exoplatform.com --- http://www.aheritier.net - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Thoughts on build vs deploy time property filtering
Before Maven, we used Ant. The build output was a tar.gz that was staged to the install host. A deploy consisted of an unpacking of the .tar.gz and Ant was run given a properties file and an installation directory. With Maven, our current process is to filter for the target environment at build time, producing an application inside .tar.gz that can be unpacked and started, but that requires one build per environment. From: Anders Hammar and...@hammar.net To: Maven Users List users@maven.apache.org Sent: Mon, November 23, 2009 4:06:11 PM Subject: Re: Thoughts on build vs deploy time property filtering Well, I would argue that you should keep all environment specific configuration outside of your artifact. How can you do filtering on deploy? Do you explode your jar/war/ear, filter, and then repack? /Anders On Mon, Nov 23, 2009 at 16:59, John Prystash stash1...@yahoo.com wrote: Hi, I was hoping for some thoughts from the community about the reasons behind why one might want to filter at build time versus at deploy time. Traditionally, our organization built one artifact from version control that still contained property placeholders. We would filter those artifacts at deploy time, so that the artifact was completed as it deployed to the target environment. This was seen as beneficial as we only had to build our artifact once, and then we can deploy that same artifact multiple times. It appears as though maven prefers to filter at build time, and create a different artifact per environment. What are the benefits of this methodology? It looks like you would have to do multiple builds (to produce an environment-specific artifact), where before, we could only build a filterable artifact once. Thanks
Re: The integration-test phase meaning?
http://www.slideshare.net/brettporter/more-apache-maven-best-practices-presentation On 24/11/2009, at 8:17 AM, Chicorio wrote: Hey Brettporter, could i have this slide as well?! thanks brettporter wrote: You're correct, though realistically a number of projects go for a separate project for this type of testing. I'm currently preparing some slides on this for my talk at ApacheCon - they should be posted after the conference. If anyone has any particular testing practices they want to see covered, let me know :) Cheers, Brett 2008/10/14 陈思淼 chensim...@gmail.com If the Project contains lots of subproject and the final project result is a Big EAR package. I think the integration-test is to put the ear package into jboss or other app server to do the test thing lots of environment variable for example: database connection parameter, the domain url, the SOA service url are different with the unit test. but the integration-test is hard to perform because of the environment difficult. I can see the maven-war-plugin have the war:run mojo binding with the integration-test , Is there any best practice who can make smooth and productive integration-test in their project, can you share with me ? -- Brett Porter http://blogs.exist.com/bporter/ -- View this message in context: http://n2.nabble.com/The-integration-test-phase-meaning-tp1331698p4054041.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Thoughts on build vs deploy time property filtering
To avoid having to build an artifact per environment we took the approach of having a single build which contains all properties for all environments, but we use a runtime flag to tell the application which set of properties to use. So inside the war (or whatever packaging you use) we have a directory structure something like this, properties/environment1/foo.properties properties/environment2/foo.properties properties/environment3/foo.properties properties/environment4/foo.properties properties/environment5/foo.properties properties/common.properties and then pass a -Denvironment=environment3 at startup which instructs our app to use the foo.properties from the environment3 directory. I'm not sure what technology you are using but we use spring which makes this type of configuration very easy. We took this approach for different reasons but it does save all the messing around with either builds per environment or filtering at deploy time. Cheers Matt On 24/11/09 08:37, John Prystash wrote: Before Maven, we used Ant. The build output was a tar.gz that was staged to the install host. A deploy consisted of an unpacking of the .tar.gz and Ant was run given a properties file and an installation directory. With Maven, our current process is to filter for the target environment at build time, producing an application inside .tar.gz that can be unpacked and started, but that requires one build per environment. From: Anders Hammarand...@hammar.net To: Maven Users Listusers@maven.apache.org Sent: Mon, November 23, 2009 4:06:11 PM Subject: Re: Thoughts on build vs deploy time property filtering Well, I would argue that you should keep all environment specific configuration outside of your artifact. How can you do filtering on deploy? Do you explode your jar/war/ear, filter, and then repack? /Anders On Mon, Nov 23, 2009 at 16:59, John Prystashstash1...@yahoo.com wrote: Hi, I was hoping for some thoughts from the community about the reasons behind why one might want to filter at build time versus at deploy time. Traditionally, our organization built one artifact from version control that still contained property placeholders. We would filter those artifacts at deploy time, so that the artifact was completed as it deployed to the target environment. This was seen as beneficial as we only had to build our artifact once, and then we can deploy that same artifact multiple times. It appears as though maven prefers to filter at build time, and create a different artifact per environment. What are the benefits of this methodology? It looks like you would have to do multiple builds (to produce an environment-specific artifact), where before, we could only build a filterable artifact once. Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
merging testng into surefire..
Good Evening All- org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested exception is java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; at org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) as you can see Surefire createSuiteFromDefinition method calls to testng which calls a nonexistent parse() routine which if corrrect would return an array XmlSuite these integration scenarios could be fleshed out more easily if surefire completely merged the testng codebase. Eventually i will find a parse routine that works from testng TestSuite if not i will of course code the missing method im wondering if testng should be merged completely into surefire to avert these types of integration errors any viable reasons to keep testng as completely separate project from sure? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. _ Windows 7: It works the way you want. Learn more. http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2
Re: merging testng into surefire..
I have never used testng -- and don't have plans too -- but it would be sensible for the test plugin to select the provider of the test engine. Paul On Mon, Nov 23, 2009 at 7:42 PM, Martin Gainty mgai...@hotmail.com wrote: Good Evening All- org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested exception is java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; at org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) as you can see Surefire createSuiteFromDefinition method calls to testng which calls a nonexistent parse() routine which if corrrect would return an array XmlSuite these integration scenarios could be fleshed out more easily if surefire completely merged the testng codebase. Eventually i will find a parse routine that works from testng TestSuite if not i will of course code the missing method im wondering if testng should be merged completely into surefire to avert these types of integration errors any viable reasons to keep testng as completely separate project from sure? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. _ Windows 7: It works the way you want. Learn more. http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: merging testng into surefire..
You can create a suite of Packages instead of defining each class to make the suite easier at 1st. --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty mgai...@hotmail.com wrote: Good Evening All- org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested exception is java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; at org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) as you can see Surefire createSuiteFromDefinition method calls to testng which calls a nonexistent parse() routine which if corrrect would return an array XmlSuite these integration scenarios could be fleshed out more easily if surefire completely merged the testng codebase. Eventually i will find a parse routine that works from testng TestSuite if not i will of course code the missing method im wondering if testng should be merged completely into surefire to avert these types of integration errors any viable reasons to keep testng as completely separate project from sure? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. _ Windows 7: It works the way you want. Learn more. http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2
RE: merging testng into surefire..
i understand paul's assertion for a separate provider suite but how would this suite of packages work? once constructed is there a way to construct integration tests to prevent potential version mismatch between provider and surefire? Thanks! Martin From: mickknut...@gmail.com Date: Mon, 23 Nov 2009 18:06:06 -0800 Subject: Re: merging testng into surefire.. To: users@maven.apache.org You can create a suite of Packages instead of defining each class to make the suite easier at 1st. --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty mgai...@hotmail.com wrote: Good Evening All- org.apache.maven.surefire.booter.SurefireExecutionException: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested exception is java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; java.lang.NoSuchMethodError: org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite; at org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150) as you can see Surefire createSuiteFromDefinition method calls to testng which calls a nonexistent parse() routine which if corrrect would return an array XmlSuite these integration scenarios could be fleshed out more easily if surefire completely merged the testng codebase. Eventually i will find a parse routine that works from testng TestSuite if not i will of course code the missing method im wondering if testng should be merged completely into surefire to avert these types of integration errors any viable reasons to keep testng as completely separate project from sure? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. _ Windows 7: It works the way you want. Learn more. http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2 _ Bing brings you maps, menus, and reviews organized in one place. http://www.bing.com/search?q=restaurantsform=MFESRPpubl=WLHMTAGcrea=TEXT_MFESRP_Local_MapsMenu_Resturants_1x1
Re: merging testng into surefire..
I do not think I fully understand the different 'Provider' concept, but if
you are looking to run different types of tests in 1 suite, then you could
create a separate PROFILE in Maven, then your suite could have something
like:
!DOCTYPE suite SYSTEM http://testng.org/testng-1.0.dtd;
suite name=Functional_TestNG verbose=1
*parameter name=providerType value=${provider.type} /*
parameter name=application-address value=
http://localhost:8889/webapp/; /
test name=Service Tests - Generic
packages
package name=com.baselogic.service /
/packages
/test
...
Or you could hard code them per test section:
test name=Service Tests - ProviderTypeA
* parameter name=providerType value=A /*
packages
package name=com.baselogic.service /
/packages
/test
test name=Service Tests - ProviderTypeB
* parameter name=providerType value=B /*
packages
package name=com.baselogic.service /
/packages
/test
Is this what you mean?
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Mon, Nov 23, 2009 at 6:46 PM, Martin Gainty mgai...@hotmail.com wrote:
i understand paul's assertion for a separate provider suite
but how would this suite of packages work?
once constructed is there a way to construct integration tests to prevent
potential version mismatch between provider and surefire?
Thanks!
Martin
From: mickknut...@gmail.com
Date: Mon, 23 Nov 2009 18:06:06 -0800
Subject: Re: merging testng into surefire..
To: users@maven.apache.org
You can create a suite of Packages instead of defining each class to make
the suite easier at 1st.
---
Thank You…
Mick Knutson, President
BASE Logic, Inc.
Enterprise Architecture, Design, Mentoring Agile Consulting
p. (866) BLiNC-411: (254-6241-1)
f. (415) 685-4233
Website: http://baselogic.com
Linked IN: http://linkedin.com/in/mickknutson
Vacation Rental: http://tahoe.baselogic.com
---
On Mon, Nov 23, 2009 at 5:42 PM, Martin Gainty mgai...@hotmail.com
wrote:
Good Evening All-
org.apache.maven.surefire.booter.SurefireExecutionException:
org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;; nested
exception is
java.lang.NoSuchMethodError:
org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
java.lang.NoSuchMethodError:
org.testng.xml.Parser.parse()Lorg/testng/xml/XmlSuite;
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.locateTestSets(TestNGXmlTestSuite.java:132)
at
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:150)
as you can see Surefire createSuiteFromDefinition method calls to
testng
which calls a nonexistent parse() routine which if corrrect would
return an
array XmlSuite
these integration scenarios could be fleshed out more easily if
surefire
completely merged the testng codebase.
Eventually i will find a parse routine that works from testng TestSuite
if
not i will of course code the missing method
im wondering if testng should be merged completely into surefire to
avert
these types of integration errors
any viable reasons to keep testng as completely separate project from
sure?
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de
confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede
unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese
Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas
le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la
copie
de ceci est interdite. Ce message sert à l'information seulement et
n'aura
pas n'importe quel effet légalement obligatoire. Étant donné que les
email
peuvent facilement être sujets à la manipulation, nous ne pouvons
accepter
aucune responsabilité pour le contenu fourni.
_
Windows 7: It works the way you want. Learn more.
http://www.microsoft.com/Windows/windows-7/default.aspx?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_evergreen:112009v2
_
Bing brings you maps, menus, and reviews
Re: [WARNING] POM is invalid. error messages in Maven 2.2.1 but not in 2.0.10
Hi Other Brett,
It's a similar problem, except that the environment settings are
coming from the shell environment and not a setttings.xml
Ellecer
On Mon, Nov 23, 2009 at 6:16 PM, Brett Randall javabr...@gmail.com wrote:
Hi Ellecer,
Is there a chance you are seeing http://jira.codehaus.org/browse/MNG-4148 ,
which is duplicated by http://jira.codehaus.org/browse/MNG-2626 ? Does that
fit your parent POM hierarchy?
Other Brett
On Mon, Nov 23, 2009 at 2:17 PM, Ellecer Valencia elle...@gmail.com wrote:
On Mon, Nov 23, 2009 at 11:18 AM, Brett Porter br...@apache.org wrote:
Did you also export WL_HOME?
I tried something similar here and it works fine in 2.2.1.
- Brett
Hi Brett,
I'd presume the environment variable being there means that's already
happened. =)
This entry is in .bashrc so I'm pretty sure the environment var is
always created.
export WL_HOME=/usr/java/weblogic
I've just created a new session window and see these errors when I run
with mvn -o -X -e package
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
Ellecer
On 23/11/2009, at 10:08 AM, Ellecer Valencia wrote:
But that's exactly the problem - it *is* defined in the environment. :(
$ls -l $WL_HOME/server/lib/webservices.jar
-rwxr-xr-x. 1 dev dev 1696324 2009-10-30 16:55
/usr/java/weblogic/server/lib/webservices.jar
$echo $WL_HOME
/usr/java/weblogic
The Maven project I am trying to build has a pom.xml with a parent pom
parent
artifactIdsuper_pom/artifactId
groupIdmypackage/groupId
version1.0.2-SNAPSHOT/version
/parent
and it's in super_pom where the weblogic dependency is declared.
On Mon, Nov 23, 2009 at 9:18 AM, Brian Fox bri...@infinity.nu wrote:
Well Maven sees it just like the message:
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped dependency
must specify an absolute path systemPath.
So since the first one works and the second one doesn't, that leads me
to believe that WL_HOME isn't defined in your environment.
On Sun, Nov 22, 2009 at 9:06 AM, Ellecer Valencia elle...@gmail.com
wrote:
Hi Brian,
Could you please clarify what's actually plain wrong about it?
Going back to the example I posted:
dependency
groupIdcom.sun/groupId
artifactIdrt/artifactId
version1.5.0.11/version
scopesystem/scope
systemPath${java.home}/lib/rt.jar/systemPath
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic/artifactId
version10.0/version
scopesystem/scope
systemPath${env.WL_HOME}/server/lib/weblogic.jar/systemPath
/dependency
Do you mean the first one, referencing ${java.home} is correct and
the one referencing ${env.WL_HOME} is wrong? So what should we do to
make it work?
thanks,
Ellecer
On Sat, Nov 21, 2009 at 4:33 AM, Brian E. Fox bri...@infinity.nu
wrote:
Maybe 2.2.2 will fix it. =)
Not likely. The pom is plain wrong an it was a bug in 2.x which
allowed it
to go unnoticed.
On Fri, Nov 20, 2009 at 3:42 PM, Brett Randall javabr...@gmail.com
wrote:
http://jira.codehaus.org/browse/MNG-4379 ... or did your team log
that
:).
On Fri, Nov 20, 2009 at 2:59 PM, Ellecer Valencia
elle...@gmail.com
wrote:
Hi Brett,
Thanks for the suggestion. I may have found the issue. Would it be
this:
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG] For managed dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG]
[DEBUG] mypackage:myartifact:jar:1.0.2:compile (selected for
compile)
[DEBUG] Skipping disabled repository central
[DEBUG] myartifact: using locally installed snapshot
[WARNING] POM for 'mypackage:myartifact:pom:1.0.2-SNAPSHOT:test'
is
invalid.
Its dependencies (if any) will NOT be available to the current
build.
[DEBUG] Reason: Failed to validate POM for project
mypackage:myartifact at Artifact
[mypackage:myartifact:pom:1.0.2-SNAPSHOT:test]
[DEBUG]
Validation Errors:
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=weblogic, version=10.0, type=jar}: system-scoped
dependency
must specify an absolute path systemPath.
[DEBUG] For dependency Dependency {groupId=weblogic,
artifactId=webservices, version=10.0,
