Re: maven-ui plugin 0.6.1 release !
Looks nice, Siegfried Goeschl mattias_xdin wrote: Mattias Olofsson is pleased to announce the maven-ui plugin 0.6.1 release! http://olofsson.homeip.net/maven-ui-plugin-site/ The maven-ui enables you to invoke goals in an GUI environment instead of at the command line. See here for sample sceenshots: http://olofsson.homeip.net/maven-ui-plugin-site/ Features in this version includes: - Changed the scanning process. Using the reactor. - Corrected bug so that maven-ui work on unix. - Changes in the gui. The plugin has been tested with Maven 1.0.2 on windows plattform. It can be installed through Maven: maven -Dmaven.repo.remote=http://www.ibiblio.org/maven,http://olofsson.homeip.net/ olof_webdav/content/maven -DartifactId=maven-ui-plugin -DgroupId=xdin -Dversion=0.6.1 plugin:download /Mattias Olofsson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Clover plugin ideas and questions
Hi Vincent, I'm not sure that I understand all of the problems you mention but I think it is important to propagate instrumented source code over multiple projects, e.g. I tweaked the clover plugin and various build to create instrumented artifacts over multiple project, where the final WAR was automatically deployed and tested with Canoo WebTest to get coverage data for the end-to-end test. I think there is some value in using this approach and not only measuring test coverage for unit tests. Hope this gives you some valuable input ... ;-) Cheers, Siegfried Goeschl Vincent Massol wrote: Hi, In preparation to implementing the clover plugin for m2, I need to understand what are the options WRT generated sources. Indeed clover modifies the source files (.java files) and generate instrumented source files. I can see 2 options: 1/ Option 1: A mechanism similar to the Ant javac task where there is a notion of pluggable compiler adapter. In that case I could write a CloverCompilerAdapter. 2/ Option 2: Generate instrumented sources in target/ somewhere and somehow convince the compile plugin to use those sources rather than the ones in src/main/java. Please note that I'd like to support the use case where main sources are instrumented and they generate clover data either when the unit tests are run or when functional tests are run or when a user manually brings up the application to test it. Also, I'd prefer that instrumented sources do not inadvertently find their way in the release and thus I'd like to keep the 2 main source trees separate (unmodified files and modified ones) so that running: m2 clover:on test:test clover:report and then: m2 install will still generate an install without instrumented sources. clover:on could act as a trigger that says use those generated sources instead of the main runtime ones. I think this would fit option 1. For option 2, it would be more like: m2 clover:test clover:report and then m2 install But this option seems less good because how do I get the WAR plugin to incorporate instrumented sources (for example) so that functional tests can be run? Any advice for doing this in m2? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: There are many ways to skin the skin the cat - WAS Re: [jira] Closed: (MPCLOVER-33) There should be a property to turn off Clover
Vincent Massol wrote: Hi Siegfried, The current solution is to have different projects sections for different needs. To my knowledge this is the only solution that currently exists. What you are really asking it seems is a generic way to express that you do not want a specific report for a specific project. This is not related to the dashboard project. This is true for any report. So you'd like to say: inherit all those reports except these few ones. Before deciding to add special properties to all plugin that generate reports I'd prefer we all agree on a strategy to express your use case. I was not suggesting that because it introduces too much work. But there are a few plugins prone to be turned off for a single project - and a simple way is a property since Maven supports property inhertiance. This is already done for the PMD and JavaNCSS plugin. ATM, why don't you use different project.xml. For example: common/ |_ top.xml |_ full_reports.xml (extends top.xml) |_ limited_reports.xml (extends top.xml) Mysubproject1 |_ project.xml (extends ../full_reports.xml) Myspecialsubproject2 |_ project.xml (extends ../limited_reports.xml) I guess using xml entity includes would also work (but not for m2 but then there are probably other mechanisms in m2 for your usecase). Another way to skin the cat :-) What do others think? Thanks -Vincent -Original Message- From: Siegfried Goeschl [mailto:[EMAIL PROTECTED] Sent: lundi 4 avril 2005 19:56 To: Maven Developers List; Vincent Massol Subject: There are many ways to skin the skin the cat - WAS Re: [jira] Closed: (MPCLOVER-33) There should be a property to turn off Clover Hi Vincent, it is quite common to use POM inheritance defining the reports and use a few exceptions : +) in fulcrum-cache there is a seperate report section to avoid the JCoverage plugin during the long running tests since it uses POM inheritance. And it drives me nuts that I have to disable my broken SIMIAN report in two project.xml +) for one of my customers I also have to redefine the reports since it would measure tons of Torque-generated code while I'm only interested that the connectivity and accessing all tables works I think the question is not necesarry if it is already possible but if it is in general sensible to turn off a report using a property :-) Thanks in advance Siegfried Goeschl Vincent Massol (JIRA) wrote: [ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ] Vincent Massol closed MPCLOVER-33: -- Resolution: Won't Fix Assign To: Vincent Massol Closing as it's already possible to do this by not adding the clover report to the project who don't want it... There should be a property to turn off Clover - Key: MPCLOVER-33 URL: http://jira.codehaus.org/browse/MPCLOVER-33 Project: maven-clover-plugin Type: Improvement Environment: Maven 1.0.2 Reporter: Wim Deblauwe Assignee: Vincent Massol It would be convenient to have a property (e.g. maven.clover.enabled) to turn Clover on or off. This is especially handy when using Clover with the multiproject plugin when some of the projects are not java projects. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
There are many ways to skin the skin the cat - WAS Re: [jira] Closed: (MPCLOVER-33) There should be a property to turn off Clover
Hi Vincent, it is quite common to use POM inheritance defining the reports and use a few exceptions : +) in fulcrum-cache there is a seperate report section to avoid the JCoverage plugin during the long running tests since it uses POM inheritance. And it drives me nuts that I have to disable my broken SIMIAN report in two project.xml +) for one of my customers I also have to redefine the reports since it would measure tons of Torque-generated code while I'm only interested that the connectivity and accessing all tables works I think the question is not necesarry if it is already possible but if it is in general sensible to turn off a report using a property :-) Thanks in advance Siegfried Goeschl Vincent Massol (JIRA) wrote: [ http://jira.codehaus.org/browse/MPCLOVER-33?page=history ] Vincent Massol closed MPCLOVER-33: -- Resolution: Won't Fix Assign To: Vincent Massol Closing as it's already possible to do this by not adding the clover report to the project who don't want it... There should be a property to turn off Clover - Key: MPCLOVER-33 URL: http://jira.codehaus.org/browse/MPCLOVER-33 Project: maven-clover-plugin Type: Improvement Environment: Maven 1.0.2 Reporter: Wim Deblauwe Assignee: Vincent Massol It would be convenient to have a property (e.g. maven.clover.enabled) to turn Clover on or off. This is especially handy when using Clover with the multiproject plugin when some of the projects are not java projects.
Re: Plugin for running an executable jar?
Hi Vincent, such a goal (javaapp:run) is found in the maven-javaapp-plugin hosted at maven-plugins.sf.net Cheers, Siegfried Goeschl Vincent Massol wrote: Hi, I'm writing some text about developing Maven plugins. I wanted to start with some simple plugin and I thought about explaining how to write a plugin to run executable jar. Of course, I'd like my sample to be something original. I just wanted to confirm here if such a goal exist somewhere in an existing Maven plugin. Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: b10
Sorry for seeming completely dumb but I was not following the MAVEN Mailing Lists for a while but +) http://jakarta.apache.org/builds/jakarta-turbine-maven/release/ only shows Beta 8 +) Current Status says the Maven B9 is currently worked on +) The link to http://cvs.apache.org/viewcvs/jakarta-turbine-maven/ is broken Cheers Siegfried Goeschl - Original Message - From: Incze Lajos [EMAIL PROTECTED] To: Maven Developers List [EMAIL PROTECTED] Sent: Monday, July 14, 2003 5:04 PM Subject: Re: b10 On Mon, Jul 14, 2003 at 04:21:47PM +0200, Siegfried Gschl wrote: Hi folks, did I miss Maven B9 or was this release dropped ?! Siegfried Goeschl CTO You missed it. It's been out for monthes. incze - 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]
