I notice, this plugin site 2.7, the code coverage report is %0 even thou
there are tests
-D
On Fri, Feb 27, 2015 at 8:33 AM, Dennis Lundberg wrote:
> I'd like to release version 2.7 of the Cobertura Maven Plugin
>
> We solved 8 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?proje
Trying to run standalone
org.codehaus.mojo:cobertura-maven-plugin:2.7:cobertura against mojo's
enchanter/enchanter-core, I got this
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] <<< cobertura-maven-plugin:2.7:cobertura (default-cli) <
[cobertura]test @ enchanter-core <<<
[INFO
Actually no build failure and the report display correctly, sorry about the
noise
On Sat, Feb 28, 2015 at 12:13 AM, Dan Tran wrote:
> Trying to run standalone
> org.codehaus.mojo:cobertura-maven-plugin:2.7:cobertura against mojo's
> enchanter/enchanter-core, I got this
>
>
> Tests run: 17, Fail
Hi all,
Forwarding here to gather opinions. Is there still any reason to keep this
plugin? I guess it's been now superceded by the maven-invoker-plugin isn't
it?
Should be move it to the graveyard? [1]
Cheers
[1] http://mojo.codehaus.org/plugins.html#Plugin_Graveyard
-- Forwarded messa
+1
On Sat, Feb 28, 2015 at 1:16 AM, Baptiste Mathus
wrote:
> Hi all,
>
> Forwarding here to gather opinions. Is there still any reason to keep this
> plugin? I guess it's been now superceded by the maven-invoker-plugin isn't
> it?
>
> Should be move it to the graveyard? [1]
>
> Cheers
>
> [1] ht
Hi,
+1 from me...
Kind regards
Karl Heinz Marbaise
On 2/28/15 10:16 AM, Baptiste Mathus wrote:
Hi all,
Forwarding here to gather opinions. Is there still any reason to keep
this plugin? I guess it's been now superceded by the
maven-invoker-plugin isn't it?
Should be move it to the graveyard?
Hi
I found this:
ossrh
https://oss.sonatype.org/content/repositories/snapshots/
false
true
in "pom.xml" file :)
2015-02-28 9:16 GMT+01:00 Dan Tran :
> Actually no build failure and the report display correctly, sorry
Should we change snapshot to sonatype repo??
On Friday, February 27, 2015, Sergei Ivanov wrote:
> Hi,
>
> I should say, if Codehaus is no more, GitHub would be my obvious first
> choice of an alternative platform.
>
> 1. Version control.
> SVN is a dinosaur and a major impediment for contributin
I have a number of internal projects which use aspectj-maven-plugin-1.7 +
java 8. they work with c-m-p-2.6, but fail with 2.7 ( note I am not
actively using cobertura in our build)
[ERROR] Failed to execute goal
org.codehaus.mojo:aspectj-maven-plugin:1.7:test-compile (default) on
project logging-
On Fri, 27 Feb 2015 12:51:18 +0100
Lennart Jörelid wrote:
> I second the opinions for moving to GitHub (or Bitbucket) instead of
> remaining in SVN.
> If doing so, I suggest we reuse as much as possible of the GitHub
> infrastructure - Wiki, Issue Tracker, Mailing lists etc.
> If we are already b
10 matches
Mail list logo
