Brett Porter <[EMAIL PROTECTED]> wrote on 30-01-2006 22:22:47: > On 1/30/06, David Sag <[EMAIL PROTECTED]> wrote: > > > > so my questions: > > 1) could someone with a working (with maven 2.0.2) cobertura plugin please > > send it to me with the correct pom.xml - jason z only sent me the compiled > > plugin without any pom.xml so it is entirely possible this is a big part > > of my problem. > > > I'll deploy a snapshot, so you can follow the instructions on the maven > website to use it. >
Okay that would be great. Will you announce it to this list when you do please? I'll focus on something else until that point. > 2) why would [mvn install site] fail, but separate [mvn install] followed by > > [mvn site] work okay? (once i have removed cobertura from the reporting) > > > I'm not sure on this one. Would need to boil it down to something simple and > reproducible to look at it I think. > shall i raise a Jira issue? Unfortunately I can't supply the pom.xml and code I am using as it's internal to the EPO. > 3) if the site phase is not supposed to trigger the compile and other phases > > then why would it be doing so, with or without the presence of thecobertura > > plugin? > > > I suspect one of the other plugins is doing this (eg surefire-report?) > hmm. there's nothing non-standard about the way I generate my surefire report so this is a bit of a mystery. > All this used to work fine using maven 2.0, and i was supposed to demo this > > last friday so you can imagine my frustration. > > > Sure, sorry about that. > > Any idea when the fixed cobertura plugin will be released properly? It's > > really not very acceptable to update the core maven project and then expect > > that we'll know to go build some plugins from source because they have been > > broken by the upgrade. I would prefer to see more comprehensive testing > > followed by simultanious release of a new core with new plugins and some > > mention in the release notes of any gotchas. As it is I am fighting an > > uphill battle to be able to recommend use of maven 2 for production systems > > as I have not been able to demonstrate that it is in fact stable for even > > pilot-project use. > > > Ok, you have to understand - the cobertura plugin has not ever been > released. Please don't generalise the situation. Simultaneous releases > should never be required as updates shouldn't break old released plugins > using documented and finalised APIs. > so you are telling me I have stumbled upon a very isolated case of the new release breaking a a plugin. Okay I can accept that. For now I will just have to make do without my lovely cobertura reports. Please let us know when you do deploy a snapshot of the working cobertura plugin however, as it really is a critical part of my project. dave
