Mojo FitNesse Plugin 1.0 Released
The FitNesse plugin team is pleased to announce the first release (1.0) of its plugin. This plugin is used to call FitNesse from your maven build and aggregates FitNesse results to your project site. HYPERLINK http://mojo.codehaus.org/fitnesse-maven-plugin/http://mojo.codehaus.org/fi tnesse-maven-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdfitnesse-maven-plugin/artifactId version1.0/version /plugin Enjoy, The FitNesse and Mojo teams Ce message Envoi est certifié sans virus connu (AVG Pro). Analyse effectuée par AVG. Version: 7.5.519 / Base de données virus: 269.22.7/1361 - Date: 05/04/2008 07:53
[ANNOUNCE] fitnesse-maven-plugin 1.0-beta-1
Hi everyone, The fitnesse plugin team is pleased to announce the release of the 1.0-beta-1. http://mojo.codehaus.org/fitnesse-maven-plugin/index.html http://fitnesse.org FitNesse is an acceptance testing framework and wiki. This plugin allows to run fitnesse during your build (remotly or locally) and aggregates a tests execution report into your site. ** Bug * [MFITNESSE-1] - Can't execute plugin * [MFITNESSE-2] - The FitNesse process is not killed when we stop the Maven build. * [MFITNESSE-3] - The plugin doesn't use properly the fitnesse conventions for page naming. It neiher use properly the type tags to override this conventions. * [MFITNESSE-4] - No picture in the result html page * [MFITNESSE-5] - Can't execute a single FitNesse Page Test * [MFITNESSE-6] - Can't use 'Expand All' or 'Collapse All' on a 'Command Line Test Results' html page * [MFITNESSE-7] - The Fitnesse plugin isn't compatible with JDK 1.4 * [MFITNESSE-8] - Error when creating report index * [MFITNESSE-10] - Can't execute Test twice ** Improvement * [MFITNESSE-13] - Add timestamp to the FitNesse result page ** Task * [MFITNESSE-11] - Mock FitnesseRunnerMojo logger in order to clean the tests execution log * [MFITNESSE-12] - Create a Jira project for Fitnesse mojo ** Wish * [MFITNESSE-14] - Have the output captured on the suite result page We'll publish a 1.0 soon. Thanks (specially to Arnaud), Philippe
RE: Maven Community news @ blog.octo.com
I know another one, more simple for beginner: clover plugin http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-clover-plugin Surprising, both projects have the same author: Vincent ;-) -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: vendredi 4 mai 2007 10:42 To: Maven Users List Subject: Re: Maven Community news @ blog.octo.com Hi Henry, Effectively, as Stephane said, you replied on the mailing list, thus I'll reply in english ;-) On 03/05/07, Stephane Nicoll [EMAIL PROTECTED] wrote: Howdy, Comments inline. Writing in English would have been more appropriate but I guess you just send the mail to the wrong recipient :) On 5/2/07, Henri Tremblay [EMAIL PROTECTED] wrote: Salut, Dommage, en fait c'était pour la mailing list, je croyais que j'avais reçu le mail personnellement. ;-) I preferred to announce it on the mailing list to be sure to not forget a maven user ;-) Je voulais envoyer un message à la liste mais puisque je t'ai sous la main, je me pose des questions sur l'avenir de maven. En fait j'ai dû mener un dur combat contre certaine limitation et je me demande ce qui est prévu. Si je te saoule, prière de m'en avertir, je referai en anglais sur la mailing list. Mais comme d'habitude les gens d'Octo sont sympas :-) Thanks. There's no problem. I always reply, not always quickly, but I reply. En fait c'est concernant les plugins. J'aimerai pouvoir faire les choses suivantes: 1- Pouvoir retirer des plugins et configurations dans des poms enfants. À priori les poms s'agrègent mais il est impossible d'en enlever des morceaux. That's an issue indeed. You can reconfigure the plugin or set the inherited flag to false to avoid spreading the config the the children. The only solution is actually to configure them in the pluginsManagement part of the pom and stop the inheritence where you want in the parent. The problem is that you have to be able to edit the parent pom. It's not possible in a child to say that it musn't use settings coming from the parent for a given plugin. 2- Avoir un certain déterminisme sur l'ordre d'exécution des plugins / exécutions. Il peut arriver que je veuille faire un antrun suivi d'un minijar suivi d'un antrun et je n'arrive pas à faire respecter cet ordre. This is scheduled for Maven 2.1 Maven 2.1-alpha-1 should be available in some weeks (we hope) 3- Pouvoir détacher un plugin d'une phase auquel il est attaché par défaut You need to create a custom lifecycle for that. This is not certainly ideal from your point's of view but it works. Some Mojos have a skip attribute which can be set to true to ... well ... skip its execution. This can maybe generalized. 4- Avoir plus clairement les versions des documentations des plugins online et les release notes en chaque version pour limiter les confusions. We're busy configuring the projects to deploy the site in a separate space per version. Not sure how far we are, Wendy might answer that. I just see, that Wendy replied. 5- Aussi, avoir des archetypes de projects: webapp, ejb, applet (en particulier applet m'intrigue) Archetype is completely re-written at the moment. As soon as it's done I'm pretty sure that we will have many archetypes available. Not sure I understand what applet means in this context. The problem with the applet must be to correctly setup the assembly (and certainly some others stuffs) to put all libraries in a given directory and create the code for the html page. 6- Connais-tu un exemple d'utilisation des phases de test d'intégration? Check the Cargo's plugin which shows how you can start/stop a container and run integration tests on them. Yes, that's also, the only one I know actually... HTH, Stéphane Arnaud Merci pour toute réponse, Henri On 5/2/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi everybody, FYI, I publish each month in French a list of news about the maven community : http://blog.octo.com/ If you are not speaking french you can however easily understand the list of releases. If I forgot something, do not hesitate to tell me. Best Regards Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud Héritier OCTO Technology [EMAIL PROTECTED] .. 50, Avenue des Champs-Elysées 75008 Paris Tél : (33) 1 58 56 10
RE: Using the POM classpath for integration testing
Hi, I just had the mechanism to the plugin. Had this parameter to use Maven POM instead of FitNesse classpath. classPathProvidermaven/classPathProvider The default value is fitnesse. The new SNAPSHOT is available in the repository. There is an example there: http://mojo.codehaus.org/fitnesse-maven-plugin/examples/multiproject.html For the implementation I use a mixed of your example and Better Builds With Maven §5.5.2. I can't use 100% of the book code, because Maven API changed. Hope it helps, Philippe -Original Message- From: Eric Torreborre [mailto:[EMAIL PROTECTED] Sent: mardi 6 mars 2007 01:24 To: Maven Users List Subject: RE: Using the POM classpath for integration testing [Please refer to the fitnesse thread regarding the fitnesse usage questions] Coming back to Maven2,... Since I would like to keep my acceptance pages along with my source files, I think I am going to need a way to launch my mojo with the project (recursive) dependencies in the classpath. Anyone knows how to do that easily? The only resource I have found that looked like that was: http://blogs.webtide.com/janb/2006/03/24/114323400.html I hope there's an easiest way, isn't? Thanks, Eric. -Original Message- From: Philippe Kernevez [mailto:[EMAIL PROTECTED] Sent: Monday, March 05, 2007 7:44 PM To: [EMAIL PROTECTED]; Eric Torreborre Subject: RE: Using the POM classpath for integration testing This is a thread that starts on Maven list. I transfer it because it more a debate about our use/pros/cons of fitnesse than a Maven2 discussion. Our process is: Before iteration * BA take stories for the next iteration, and write test data (only data tables and comments ). During iteration * dev take a story and try to implement corresponding code. For doing this they: ** develop some code ** interact with BA if they discover some conflict ** enrich FitNesse page with Fixture names, parameters, etc. * CI: integrate and deploy to a shared Fitnesse server * HML (homologation)/BA re-run tests. All work on the server pages that are our tests referential. In your case the tests referential is Svn. In fact we prefer (and try to think about) to have the tests referential at the same place/tools than the code. But, we choose to keep an always available centralized server. All people (including non team member) can see the tests implementation advancement. We add few troubles with the centralizer fitnesse server. The drawbacks I see with this approach are: * We don't have the same referential for code and tests * we need to manage release/tags manually with FitNesse wiki copy. * We can't easily (without a dev help) replay older revision tests. In fact, these drawbacks are acceptable for us while we work on small iterations; most of the effort is on the trunk. I we had long time branch development; I may prefer your approach. My paradise would be to substitute the FitNesse version mechanism with Subversion revision. ;-) -Original Message- From: Eric Torreborre [mailto:[EMAIL PROTECTED] Sent: lundi 5 mars 2007 06:09 To: Maven Users List Subject: RE: Using the POM classpath for integration testing Hi Philippe, Here is the setup I have in mind. Not only in mind, this is what I previously did, excepted that we were using Ant. c:/.../project/src/main/java: production code c:/.../project/src/test/java/fixtures: fitnesse fixtures c:/.../project/src/test/resources/specs: fitnesse pages c:/.../tools/fitnesse/run_project.bat using fitnesse.jar from the maven repository and having FIT_SPECS=c:/.../project/src/test/resources/specs Then we can work like that: -developers: -develop the fixtures, -use Fitnesse locally to modify Fitnesse pages as necessary and commit -use the FitnesseRunner class to debug their fixtures -use maven-fitnesse-plugin to do a mvn install passing the acceptance tests -business analysts: -run Fitnesse locally against a proper version tag from the VCS (usually HEAD) and commit new pages if necessary -use a deployment server with the latest version (SNAPSHOT or production release) to play with the latest soft. But nothing written here is ever committed to the VCS -continuous integration server: -use maven-fitnesse-plugin to run the acceptance tests against the last version -updates the deployment server with the latest ok-release The important point is that there can be a shared Fitnesse server but only as a sandbox environment to play with the latest release. If business analysts need to commit pages, they have to test them first on their private Fitnesse server. The overall process that I would use is: -BA+dev: take a story -BA: create (or update) a Fitnesse page for it -BA: commit it (don't integrate it yet to the executed acceptance tests) -Dev: code the fixtures, test the page, commit (add the page to the acceptance test suite) -CI env: integrate and deploy to a shared Fitnesse server -BA: re
RE: Using the POM classpath for integration testing
: vendredi 2 mars 2007 02:27 To: Maven Users List Subject: RE: Using the POM classpath for integration testing Philippe, By the way, I had a different approach for executing the Fitnesse tests. I wrote a FitnessePageRunner class based on the FolderRunner class in the fitlibrary. This way, I don't have to launch a web server to do the job. The FitnessePageRunner: -converts content.txt files to html pages using Fitnesse classes -runs the FolderRunner class -analyzes the indexReport.html page to get the results fitnesse-runner is a separate project so I can reuse this class to debug my application if necessary. What do you think of this approach? Eric. -Original Message- From: Philippe Kernevez [mailto:[EMAIL PROTECTED] Sent: Friday, March 02, 2007 2:36 AM To: 'Maven Users List' Subject: RE: Using the POM classpath for integration testing Hi Eric, Do you speak about the fitnesse-maven-plugin ? I suppose that's the case. The plugin doesn't use the POM dependencies because they are supposed to be specified in the Fitnesse page. The plugin provides a solution to change the server classpath (with string substitution), this allows to have an unix fitnesse server and to run the tests on a windows plateform. I didn't write any documentation yet :-( But, this is my next task. You may yet find an example with this sample: https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/fitnesse-maven-plu gin/ src/it/minimalist/pom.xml The classPathSubstitutions tag allows configuring the plugin for this use. You can also add dependencies to your plugin (like Fitnesse), they will be add to Fitnesse dependencies. In your case, you will have to define twice your dependency, and it wont be nice. We could and a tag to know if we want to add the current project dependencies to FitNesse. Does it answer to your question? Philippe Kernevez (Did we meet in Paris in SITI project ?) -Original Message- From: Eric Torreborre [mailto:[EMAIL PROTECTED] Sent: jeudi 1 mars 2007 07:46 To: users@maven.apache.org Subject: Using the POM classpath for integration testing Hi, I have written a simple maven plugin that runs Fitnesse pages during the integration-test phase. However, it looks like this plugin, when executed, does not find the classes that should be provided by the POM (along with dependencies). Is there is configuration that should be done, in order to make the plugin aware of the POM classes? I am certainly missing something very simple, I just don't know what! Thanks, Eric. Eric TORREBORRE Senior Technical Analyst Professional Services Asia-Pacific . C A L Y P S O Level 15, JT Building. 2-2-1 Toranomon, Minato-ku, Tokyo 105-0001 OFFICE +81-(0)3-5114-8262 FAX +81-(0)3-5114-8263 . www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using the POM classpath for integration testing
Hi Eric, Do you speak about the fitnesse-maven-plugin ? I suppose that's the case. The plugin doesn't use the POM dependencies because they are supposed to be specified in the Fitnesse page. The plugin provides a solution to change the server classpath (with string substitution), this allows to have an unix fitnesse server and to run the tests on a windows plateform. I didn't write any documentation yet :-( But, this is my next task. You may yet find an example with this sample: https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/fitnesse-maven-plugin/ src/it/minimalist/pom.xml The classPathSubstitutions tag allows configuring the plugin for this use. You can also add dependencies to your plugin (like Fitnesse), they will be add to Fitnesse dependencies. In your case, you will have to define twice your dependency, and it wont be nice. We could and a tag to know if we want to add the current project dependencies to FitNesse. Does it answer to your question? Philippe Kernevez (Did we meet in Paris in SITI project ?) -Original Message- From: Eric Torreborre [mailto:[EMAIL PROTECTED] Sent: jeudi 1 mars 2007 07:46 To: users@maven.apache.org Subject: Using the POM classpath for integration testing Hi, I have written a simple maven plugin that runs Fitnesse pages during the integration-test phase. However, it looks like this plugin, when executed, does not find the classes that should be provided by the POM (along with dependencies). Is there is configuration that should be done, in order to make the plugin aware of the POM classes? I am certainly missing something very simple, I just don't know what! Thanks, Eric. Eric TORREBORRE Senior Technical Analyst Professional Services Asia-Pacific . C A L Y P S O Level 15, JT Building. 2-2-1 Toranomon, Minato-ku, Tokyo 105-0001 OFFICE +81-(0)3-5114-8262 FAX +81-(0)3-5114-8263 . www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
