Re: How can Maven be used to prepare a complex, multi-module JavaEE app for release
2012/1/10 Glenn Silverman gsilver...@dispensingsolutionsinc.com Why not use the maven-release-plugin to eliminate the manual process, you might wonder? Great, then I have to modify each POMs scm element whenever I do a SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at some point, the release plugin isn't going to recurse through all of the changed modules for me. I think you answered yourself. Move to a multi-module POM+. Moreover, you wrote about a complex application made up of several wars, besides other artifacts. Do you mean that, in the end, you have a single EAR? Antonio
Re: How can Maven be used to prepare a complex, multi-module JavaEE app for release
You might want to take a look at the versions plugin (http://mojo.codehaus.org/versions-maven-plugin/) to change the root POM and make the child modules fall in line (update-child-modules goal). Best maven practice seems to be that you don't try to release part of a hierarchy. If there are modules that shouldn't be released, put them elsewhere (and release them individually or as part of another hierarchy). If there are modules that could be released but needn't be released (because they don't contain changes), it's usually easiest to release them anyway rather then bend yourself backwards. On Tue, Jan 10, 2012 at 9:42 AM, Antonio Petrelli antonio.petre...@gmail.com wrote: 2012/1/10 Glenn Silverman gsilver...@dispensingsolutionsinc.com Why not use the maven-release-plugin to eliminate the manual process, you might wonder? Great, then I have to modify each POMs scm element whenever I do a SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at some point, the release plugin isn't going to recurse through all of the changed modules for me. I think you answered yourself. Move to a multi-module POM+. Moreover, you wrote about a complex application made up of several wars, besides other artifacts. Do you mean that, in the end, you have a single EAR? Antonio - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to run a maven goal when there is tests failures?
Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier.
Re: How to run a maven goal when there is tests failures?
On Tuesday 10 January 2012 Xavier S. wrote: Hello, I would like to know if there is a way to execute a goal when there is test failures? Use mvn -DskipTests. You can also try mvn -Dmaven.test.skip=true, which is a bit longer and not only skips test execution but also skips test compilation. hth, - martin signature.asc Description: This is a digitally signed message part.
Re: How to run a maven goal when there is tests failures?
you'd need to do something like failsafe, where the execution is separated from the checking and failing the build might even get what you want using just failsafe On 10 January 2012 13:05, Xavier S. xavier.seign...@gmail.com wrote: Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
You can configure the maven surefire plugin to ignore errors (not the default). Look at the Maven Surefire plugin documentation. Regards Jeff MAURY -- Forwarded message -- From: Xavier S. xavier.seign...@gmail.com Date: Tue, Jan 10, 2012 at 2:05 PM Subject: How to run a maven goal when there is tests failures? To: Maven Users List users@maven.apache.org Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier. -- Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: How to run a maven goal when there is tests failures?
You can just skip the test. To do so you have multiple solution. Comment out all you test which could be long and error prone. Remove them from you testSuite, which dependly hardly on your plateform. And pass a special command to maven http://maven.apache.org/general.html#skip-test Or you can make some special profile for that. Le 10 janvier 2012 08:05, Xavier S. xavier.seign...@gmail.com a écrit : Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier. -- Benjamin Dreux Analyste-Programmeur Chaire de logiciel libre-Finance Social et solidaire UQAM Montréal - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: How to run a maven goal when there is tests failures?
what about http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S. xavier.seign...@gmail.comwrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier -- Legacy code often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
Re: How to run a maven goal when there is tests failures?
Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.comwrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: Mvn commands are stalling
I think what Robert mentioned was the root of my problems - I did not think to look inside the pom.xml file, and it was also because I was having others problems and I thought erroneously that they may be interlinked. Also, since my pom.xml was generated by maven itself, it did not occur to me that it may need to be edited. I was subconsciously thinking Maven generated it for me, I need not touch it, it must be good Thanks for all your help. I really appreciate your time and ideas!! On Mon, Jan 9, 2012 at 12:52 PM, Brian Topping topp...@codehaus.org wrote: On Jan 9, 2012, at 12:01 PM, Robert Scholte wrote: Even though I'm not a newbie, I can see 2 potential problems with this sentence: 1. line 84, column 15 of what? It doesn't mention the file. Sure, it always about the poms, but we're talking about unexperienced users here. 2. build.plugins.plugin.version ? This doesn't look like xml, so maybe you're not triggered to look inside the pom. And if you use a pom-editor, you may have never seen the xml. Another observation I might try to append to Robert's list is how to separate the signal from the noise. My personal opinion is that Maven is pretty chatty, which is great for experienced users, but a bit overwhelming for some new users. One option would be to reduce verbosity, but that doesn't really serve experienced users well. Another option would be what Karaf has done and that is to use colorized logs. http://blog.uncommons.org/2006/04/09/colour-coded-console-logging-with-log4j/covers the gist of it. The ANSI colorization characters are kind of ugly in terminals that aren't set up correctly, but it might help improve readability? Brian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
Thanks Guillaume! That's exactly what I want to do. So people, any idea? Regards, Xavier 2012/1/10 Guillaume Polet guillaume.po...@gmail.com Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/**plugins/maven-surefire-plugin/**test-mojo.html# **testFailureIgnorehttp://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.com** wrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/**mvnref-book/reference/running-** sect-options.htmlhttp://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: How can Maven be used to prepare a complex, multi-module JavaEE app for release
We had the same situation. One of the things that we did as the application got more mature was to decide that not all modules need to be at the same version number. This was just an abstraction of the idea that we had already accepted that third party libraries had different version number and worked just fine. We did have an architecture that was functionally organized so we did get to a state where minor releases (1.x to 1.y) did not actually require code changes in the majority of modules. We used Hibernate for the ORM and had an API for database access and a lot of web services which helped insulate the view from the model. In the planning phase, we identified the modules that would be changed and created a simple spreadsheet that we used to control the versions in each release. This reduced the overhead and removed the frustration of having to rebuild modules just to change a version number. In reality, changing all the modules' versions was not a major consumer of time but more of an annoyance at doing something for no useful purpose. Ron On 09/01/2012 8:07 PM, Glenn Silverman wrote: We have a complex JavaEE app with multiple wars, jars, ds.xml and config files, etc. In fact, there are over 80 different artifacts that make up our application. We use the maven-assembly-plugin to create a gzip file and untar it into a JBOSS instance to deploy and run. It's not pretty and it's a nightmare to actually do a release. We use Subversion, Maven 3, Nexus for repository management and Jenkins for build management. The following are the manual steps required for us to do a release: 1. Create a SNAPSHOT version of the changed modules and deploy to a test environment a. Create a SNAPSHOT branch in SVN b. Copy changed modules to the new branch from trunk c. Manually change the dependency versions from SNAPSHOT as needed in each individual POM d. Manually change the dependency versions in the assembly POM files (there are 5 sub assemblies and one main assembly to put them all together) e. Run mvn deploy on each new module to install SNAPSHOT versions to Nexus f.Run mvn install on each sub-assembly (I don't want to deploy the assemblies to Nexus) g. Run mvn package on the main assembly h. Copy and untar the main assembly on our QA JBOSS server/instance 2. Create a RELEASE version and deploy to production a. Merge the SNAPSHOT branch modules in SVN to trunk b. Repeat steps a-h, above, manually removing -SNAPSHOT from all the POM files I've tried to simplify a little by consolidating dependency management in the parent assembly, but it still requires that I modify each affected sub-assembly to use the correct parent version. Why not use the maven-release-plugin to eliminate the manual process, you might wonder? Great, then I have to modify each POMs scm element whenever I do a SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at some point, the release plugin isn't going to recurse through all of the changed modules for me. I thought maven was supposed to relieve me of this manual configuration nightmare, but it seems to only have increased it. All of the documentation and Web-help I have seen discusses only simple multi-module systems, with maybe a war, an ejb and a domain jar, for example. That's child's play compared to what we have to deal with, and I'm just out of ideas. Maybe someone out there has faced a similar daunting task and can help. Thanks in advance. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to run a maven goal when there is tests failures?
use failsafe. parse the failsafe results yourself... if they show a test failure, do your special thing then let failsafe verify stop the build - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 16:58, Xavier S. xavier.seign...@gmail.com wrote: Thanks Guillaume! That's exactly what I want to do. So people, any idea? Regards, Xavier 2012/1/10 Guillaume Polet guillaume.po...@gmail.com Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/**plugins/maven-surefire-plugin/**test-mojo.html# **testFailureIgnore http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.com** wrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/**mvnref-book/reference/running-** sect-options.html http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: How to run a maven goal when there is tests failures?
given that nobody else bothered to read the original question, it does not surprise me that nobody bothered to read my original answer of using failsafe ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 18:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: use failsafe. parse the failsafe results yourself... if they show a test failure, do your special thing then let failsafe verify stop the build - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 16:58, Xavier S. xavier.seign...@gmail.com wrote: Thanks Guillaume! That's exactly what I want to do. So people, any idea? Regards, Xavier 2012/1/10 Guillaume Polet guillaume.po...@gmail.com Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/**plugins/maven-surefire-plugin/**test-mojo.html# **testFailureIgnore http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.com ** wrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/**mvnref-book/reference/running-** sect-options.html http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
RE: How can Maven be used to prepare a complex, multi-module JavaEE app for release
I really appreciate all the feedback so far. I see the problem as one of build promotion, where you have a multi-module application with a non-flat physical structure in Subversion; i.e.; the modules are nested two or three deep, with a hierarchy of parent POM files. The actual assembly module is, itself, a non-flat structure, with a hierarchy of sub-assemblies. As I mentioned initially, I use POM inheritance, not aggregation. What I would like to do is control build-promotion from a single top-level POM file, if that is possible. -Original Message- From: Ron Wheeler [mailto:rwhee...@artifact-software.com] Sent: Tuesday, January 10, 2012 9:39 AM To: users@maven.apache.org Subject: Re: How can Maven be used to prepare a complex, multi-module JavaEE app for release We had the same situation. One of the things that we did as the application got more mature was to decide that not all modules need to be at the same version number. This was just an abstraction of the idea that we had already accepted that third party libraries had different version number and worked just fine. We did have an architecture that was functionally organized so we did get to a state where minor releases (1.x to 1.y) did not actually require code changes in the majority of modules. We used Hibernate for the ORM and had an API for database access and a lot of web services which helped insulate the view from the model. In the planning phase, we identified the modules that would be changed and created a simple spreadsheet that we used to control the versions in each release. This reduced the overhead and removed the frustration of having to rebuild modules just to change a version number. In reality, changing all the modules' versions was not a major consumer of time but more of an annoyance at doing something for no useful purpose. Ron On 09/01/2012 8:07 PM, Glenn Silverman wrote: We have a complex JavaEE app with multiple wars, jars, ds.xml and config files, etc. In fact, there are over 80 different artifacts that make up our application. We use the maven-assembly-plugin to create a gzip file and untar it into a JBOSS instance to deploy and run. It's not pretty and it's a nightmare to actually do a release. We use Subversion, Maven 3, Nexus for repository management and Jenkins for build management. The following are the manual steps required for us to do a release: 1. Create a SNAPSHOT version of the changed modules and deploy to a test environment a. Create a SNAPSHOT branch in SVN b. Copy changed modules to the new branch from trunk c. Manually change the dependency versions from SNAPSHOT as needed in each individual POM d. Manually change the dependency versions in the assembly POM files (there are 5 sub assemblies and one main assembly to put them all together) e. Run mvn deploy on each new module to install SNAPSHOT versions to Nexus f.Run mvn install on each sub-assembly (I don't want to deploy the assemblies to Nexus) g. Run mvn package on the main assembly h. Copy and untar the main assembly on our QA JBOSS server/instance 2. Create a RELEASE version and deploy to production a. Merge the SNAPSHOT branch modules in SVN to trunk b. Repeat steps a-h, above, manually removing -SNAPSHOT from all the POM files I've tried to simplify a little by consolidating dependency management in the parent assembly, but it still requires that I modify each affected sub-assembly to use the correct parent version. Why not use the maven-release-plugin to eliminate the manual process, you might wonder? Great, then I have to modify each POMs scm element whenever I do a SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at some point, the release plugin isn't going to recurse through all of the changed modules for me. I thought maven was supposed to relieve me of this manual configuration nightmare, but it seems to only have increased it. All of the documentation and Web-help I have seen discusses only simple multi-module systems, with maybe a war, an ejb and a domain jar, for example. That's child's play compared to what we have to deal with, and I'm just out of ideas. Maybe someone out there has faced a similar daunting task and can help. Thanks in advance. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to run a maven goal when there is tests failures?
Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier.
Warning when using expression for version in pom.xml
I am investigating the use of an expression for the value of the version in
the pom.xml. There are properties that fully specify the actual value of
the version in the same pom.xml, so I'm not sure why the warning is issued.
The expression is correctly evaluated (i.e., value = 1.2.0-67936). The
purpose of the expression is to help support continuous delivery - see the
following link for more details on this approach:
https://groups.google.com/d/msg/continuousdelivery/hdlALMDuiyU/brtjqCqyFd4J
So my question is: Will this warning turn into a fatal build error in the
future?
*warning message
*
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for com.foo.library:continuous-delivery:jar:1.2.0-67936
[WARNING] 'version' contains an expression but should be a constant. @
com.foo.library:continuous-delivery:${main.version}-${build.number},
/export/home/patp/CONTINUOUS_DELIVERY/VERSION/continuous-delivery/pom.xml,
line 13, column 11
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
*relevant bits from pom.xml*
/Note that SNAP is default value for svn.revision; alternate value comes
from svn revision number as -Dsvn.revision=67936 in the example:/
groupIdcom.foo.library/groupId
artifactIdcontinuous-delivery/artifactId
version${main.version}-${build.number}/version
. . .
properties
svn.revisionSNAP/svn.revision
build.number${svn.revision}/build.number
main.version1.2.0/main.version
/properties
--
View this message in context:
http://maven.40175.n5.nabble.com/Warning-when-using-expression-for-version-in-pom-xml-tp5134463p5134463.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
howto simply export dependent jars someplace
I have the following task, which should be simple. I'm having a brain cramp but I can't figure out how to do it. I am building a straight java application with dependencies. Under normal circumstances, I can get what I need painlessly by using the maven assembly plugin and building a jar-with-dependencies. However, the end goal here is that this application runs on a number of workstations, to which new versions would be pushed if available by an outside legacy process (not maven). In this scenario we simply wish to have the dependent jars (which will change rarely, if ever) in a lib directory on each machine, and an executable jar with a manifest putting all the jars on the classpath. I simply want to extract all the dependent jars from the repository into a directory. This collection can then be copied out to the production servers. What, if any, maven goal/lifecycle phase allows me to gather all the dependent jars someplace without manually picking each one out of my local repo? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: howto simply export dependent jars someplace
Greetings, Try dependency:copy-dependencies -Jesse On Jan 10, 2012 5:23 PM, Steve Cohen sco...@javactivity.org wrote: I have the following task, which should be simple. I'm having a brain cramp but I can't figure out how to do it. I am building a straight java application with dependencies. Under normal circumstances, I can get what I need painlessly by using the maven assembly plugin and building a jar-with-dependencies. However, the end goal here is that this application runs on a number of workstations, to which new versions would be pushed if available by an outside legacy process (not maven). In this scenario we simply wish to have the dependent jars (which will change rarely, if ever) in a lib directory on each machine, and an executable jar with a manifest putting all the jars on the classpath. I simply want to extract all the dependent jars from the repository into a directory. This collection can then be copied out to the production servers. What, if any, maven goal/lifecycle phase allows me to gather all the dependent jars someplace without manually picking each one out of my local repo? --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
releasing a multi-modult project
I inherited a multi-module project from someone that is no-longer with the company. I have Maven experience, but not with multi-module projects. Release prepare is succeeding for the first module, and is skipping the remainder of the modules. How do I get release prepare to prepare all modules? NFO] [INFO] Reactor Summary: [INFO] [INFO] Production . SUCCESS [13.131s] [INFO] Hibernate Service .. SKIPPED [INFO] Production Commons . SKIPPED [INFO] Host Adapter ... SKIPPED [INFO] Web Service Host .. SKIPPED [INFO] Web Service Client SKIPPED [INFO] File Host Adapter Service .. SKIPPED [INFO] HostAdapterService SKIPPED [INFO] Socket Host Adapter Service SKIPPED [INFO] Engineering Client Service SKIPPED [INFO] Standard Service ... SKIPPED [INFO] High Availability Service .. SKIPPED [INFO] Production Web Application . SKIPPED [INFO] Step One ... SKIPPED [INFO] Production Utilities ... SKIPPED [INFO] Production License Creator . SKIPPED [INFO] Configuration Service .. SKIPPED [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 13.917s [INFO] Finished at: Tue Jan 10 17:51:03 EST 2012 [INFO] Final Memory: 5M/15M Thanks, GB
RE: How to run a maven goal when there is tests failures?
- One has to write custom goal and attach to the test phase of maven build life cycle. Goal checks if test failure and do the action. http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Regards, Yuvaraj -Original Message- From: Xavier S. [mailto:xavier.seign...@gmail.com] Sent: Tuesday, January 10, 2012 5:45 PM To: Maven Users List Subject: How to run a maven goal when there is tests failures? Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier.
Re: using Stub generated by wadl2java (REST Client)
hi.. thanks for the reply. But I was not able to find a suitable forum regarding this. If you know any of them, please share with me. thx a lot -- View this message in context: http://maven.40175.n5.nabble.com/using-Stub-generated-by-wadl2java-REST-Client-tp5125364p5136004.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: using Stub generated by wadl2java (REST Client)
But I was not able to find a suitable forum regarding this. If you know any of them, please share with me. I don't use wadl so I don't know what forum(s) to use. I checked Google and it suggested a java.net website. I'm sure you can find it (and the mailing lists linked to it) if you do your own searching. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven migration
Hi Karl Heinz Marbaise, How are doing... I installed nexus repository.i created hosted repository and added all artifacts. How to add maven plugins to repository.i added maven-resource-plugin. it could ask the org.apache and org.codehaus.plexes ...some time it shows maven-parent-18.pom My aim is using only company repository.(These repository contains jar+pluings) Plz help me. Regards, chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5136233.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: How to run a maven goal when there is tests failures?
:) Sorry, I missed your answer in the noise! I'll give it a try and let you know. (I hope it won't have side effects using failsafe rather than surefire). Regards, Xavier 2012/1/10 Stephen Connolly stephen.alan.conno...@gmail.com given that nobody else bothered to read the original question, it does not surprise me that nobody bothered to read my original answer of using failsafe ;-) - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 18:16, Stephen Connolly stephen.alan.conno...@gmail.com wrote: use failsafe. parse the failsafe results yourself... if they show a test failure, do your special thing then let failsafe verify stop the build - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 10 Jan 2012 16:58, Xavier S. xavier.seign...@gmail.com wrote: Thanks Guillaume! That's exactly what I want to do. So people, any idea? Regards, Xavier 2012/1/10 Guillaume Polet guillaume.po...@gmail.com Tell me if I am wrong Xavier, but I think that what he would like to do is perform something special when the tests fail, not just skip them or not fail the build. My guess would be that he is expecting some kind of on failure/on tests failure phase where he could attach other maven plugins to perform alternate behaviour. Unfortunately I have no idea on how this could be done. Probably using Ant or by writing your own plugin, but I find both solutions quite poor. Maybe Maven is not the tool to be used to perform this. Although you can do a lot of things with Maven, sometimes bending its original objectives too far away is just cumbersome and counter-productive /(not sure this english, btw). /Cheers, Guillaume Le 10/01/2012 17:22, Jeff MAURY a écrit : what about http://maven.apache.org/**plugins/maven-surefire-plugin/**test-mojo.html# **testFailureIgnore http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#testFailureIgnore Jeff MAURY On Tue, Jan 10, 2012 at 4:55 PM, Xavier S.xavier.seign...@gmail.com ** wrote: Thanks for all your answers, but I think I should re explain my need. I don't want to skip the tests. The default fail fast mode of maven suits me (section 6.1.8 http://www.sonatype.com/books/**mvnref-book/reference/running-** sect-options.html http://www.sonatype.com/books/mvnref-book/reference/running-sect-options.html ). I just want to run my custom mojo just after my tests failures and just before the end of the maven execution (if there is build failures, maven do not even finishes the current test phase). Regards, Xavier
Re: How to run a maven goal when there is tests failures?
I'm not sure it will work since when there is test failures the test phase is not executed completely and stops on the failing goal within that phase. Regards, Xavier 2012/1/11 Yuvaraj Vanarase yuvaraj.vanar...@synechron.com - One has to write custom goal and attach to the test phase of maven build life cycle. Goal checks if test failure and do the action. http://maven.apache.org/guides/plugin/guide-java-plugin-development.html Regards, Yuvaraj -Original Message- From: Xavier S. [mailto:xavier.seign...@gmail.com] Sent: Tuesday, January 10, 2012 5:45 PM To: Maven Users List Subject: How to run a maven goal when there is tests failures? Hello, I would like to know if there is a way to execute a goal when there is test failures? Since maven stops its execution (fail fast mode) after encountering a test failure, is there any options to launch a goal between that test failure and he stop of maven? Regards, Xavier.
