This is great news, thanks for the update! Any idea when version 2.1 will be available through iBiblio? I can't seem to find the snapshot release.
Cheers, GB Joakim Erdfelt-2 wrote: > > Funny that this should come up. > > I just committed MCOBERTURA-46 (Upgrade to cobertura 1.8) just a minute > ago. > > There is a bug in the datafile location setting ability in cobertura 1.8 > I have arranged a patch on the cobertura side, but need help from other > interested parties to get it commited into the cobertura codebase. > > See: > https://sourceforge.net/tracker/index.php?func=detail&aid=1543280&group_id=130558&atid=720017 > > - Joakim Erdfelt > > > Wayne Fay wrote: >> This can only happen with a new cobertura-maven-plugin release, which >> is up to the owners of the c-m-p plugin. >> >> You will probably need to speak with them directly to find out when >> they plan a new release of this plugin, etc. >> >> Wayne >> >> On 8/22/06, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote: >>> >>> >>> Jimisola Laursen wrote: >>> > >>> > Hi! >>> > >>> > Not sure who is responsible, but I've been trying to make >>> > cobertura-maven-plugin use cobertura 1.8 instead of 1.7 due to >>> problems >>> > with AspectJ. >>> > >>> > In the process of this I get the error below and it looks as if the >>> > deployed cobertura 1.8 contains errors. Not sure of who can fix this I >>> > post this here. >>> > >>> > Regardsm >>> > Jimisola >>> > >>> > [WARNING] POM for 'cobertura:cobertura:pom:1.8:runtime' is invalid. It >>> > will be ignored for artifact resolution. Reason: Parse error >>> reading POM. >>> > Reason: expected START_TA >>> > G or END_TAG not TEXT (position: TEXT seen ...</version>\r\n >>> > <url>http://asm.objectweb.org</... @12:38) >>> > [DEBUG] Reason: Parse error reading POM. Reason: expected START_TAG or >>> > END_TAG not TEXT (position: TEXT seen ...</version>\r\n >>> > <url>http://asm.objectweb.org</... @12 >>> > :38) >>> > >>> > >>> > >>> >>> About the fact that the cobertura-maven-plugin still uses Cobertura >>> 1.7 and >>> not 1.8: will this be fixed eventually? I'm running into the same >>> problems >>> with AspectJ here. Of course I could just update our local POM >>> files, but I >>> would prefer the cleaner solution :) >>> >>> Cheers, >>> GB >>> -- >>> View this message in context: >>> http://www.nabble.com/Cobertura-1.8-pom-%28on-ibiblio%29-contains-errors-and-is-invalid-tf2058878.html#a5921143 >>> >>> >>> Sent from the Maven - Users forum at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> 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] > > > -- View this message in context: http://www.nabble.com/Cobertura-1.8-pom-%28on-ibiblio%29-contains-errors-and-is-invalid-tf2058878.html#a5941527 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
